Polypeptdes capable of forming homo-oligomers with modular hydrogen bond network-mediated specificity and their design

ABSTRACT

Methods and apparatus for identifying and screening hydrogen bond networks are provided. A computing device can determine a search space for hydrogen bond networks related to one or more molecules, where the search space can include a plurality of energy terms related to a plurality of residues related to the hydrogen bond networks. The computing device can search the search space to identify one or more hydrogen bond networks based on the plurality of energy terms. The computing device can screen the identified hydrogen bond networks to identity one or more screened hydrogen bond networks based on scores for the identified hydrogen bond networks. An output can be generated that is related to the one or more screened hydrogen bond networks. Also provided are polypeptides that can form homo-oligomers with modular hydrogen bond network-mediated specificity.

RELATED APPLICATION

This application is a U.S. national phase of International Application No. PCT/US2017/025532, filed on Mar. 31, 2017, which claims priority to U.S. Provisional Application No. 62/317,190, filed Apr. 1, 2016, both of which are incorporated by reference herein in their entirety.

BACKGROUND

Hydrogen bonds play key roles in the structure, function, and interaction specificity of biomolecules. There are two main challenges facing do novo design of hydrogen bonding interactions: first, hydrogen bonding atoms are geometrically restricted to narrow ranges of orientation and distance, and second, nearly all polar atoms must participate in hydrogen bonds either with other macromolecular polar atoms, or with solvent—if not, there is a considerable energetic penalty associated with stripping away water upon folding or binding. The DNA double helix elegantly resolves both challenges; paired bases come together such that all buried polar atoms make hydrogen bonds that are self-contained between the two bases and have near ideal geometry. In proteins, meeting these challenges is more complicated because backbone geometry is highly variable and pairs of polar amino acids cannot generally interact as to fully satisfy their mutual hydrogen bonding capabilities; hence sidechain hydrogen bonding usually involves networks of multiple amino acids with variable geometry and composition, and there are generally very different networks at different sites within a single protein or interface pre-organizing polar residues for binding and catalysis.

SUMMARY OF THE INVENTION

In nature, structural specificity in DNA and proteins is encoded quite differently: in DNA, specificity arises from modular hydrogen bonds in the core of the double helix, whereas in proteins, specificity arises largely from buried hydrophobic packing complemented by irregular peripheral polar interactions. Herein is described a general approach for designing a wide range of protein homo-oligomers with specificity determined by modular arrays of central hydrogen bond networks. This approach can be used to design dimers, trimers, and tetramers comprising two concentric rings of helices, including previously not seen triangular, square, and supercoiled topologies. X-ray crystallography confirms that the structures overall, and the hydrogen bond networks in particular, are nearly identical to the design models, and the networks confer interaction specificity in vivo. The ability to design extensive hydrogen bond networks with atomic accuracy is a milestone for protein design and enables the programming of protein interaction specificity for a broad range of synthetic biology applications. Also described herein is a class of protein oligomers with regular arrays of hydrogen bond networks that enable programming of interaction specificity.

In one aspect, a method is provided. A computing device determines a search space for hydrogen bond networks related to one or more molecules. The search space includes a plurality of energy terms related to a plurality of residues related to the hydrogen bond networks. The computing device searches the search space to identify one or more hydrogen bond networks based on the plurality of energy terms. The computing device screens the identified one or more hydrogen bond networks to identify one or more screened hydrogen bond networks based on scores for the one or more identified hydrogen bond networks. The computing device generates an output related to the one or more screened hydrogen bond networks.

In another aspect, a computing device is provided. The computing device includes one or more data processors and a computer-readable medium. The computer-readable medium is configured to store at least computer-readable instructions that, when executed, cause the computing device to perform functions. The functions include: determining a search space for hydrogen bond networks related to one or more molecules, where the search space includes a plurality of energy terms related to a plurality of residues related to the hydrogen bond networks; searching the search space to identify one or more hydrogen bond networks based on the plurality of energy terms; screening the identified one or more hydrogen bond networks to identify one or more screened hydrogen bond networks based on scores for the one or more identified hydrogen bond networks; and generating an output related to the one or more screened hydrogen bond networks.

In another aspect, a computer-readable medium is provided. The computer-readable medium is configured to store at least computer-readable instructions that, when executed by one or more processors of a computing device, cause the computing device to perform functions. The functions include: determining a search space for hydrogen bond networks related to one or more molecules, where the search space includes a plurality of energy terms related to a plurality of residues related to the hydrogen bond networks; searching the search space to identify one or more hydrogen bond networks based on the plurality of energy terms; screening the identified one or more hydrogen bond networks to identify one or more screened hydrogen bond networks based on scores for the one or more identified hydrogen bond networks; and generating an output related to the one or more screened hydrogen bond networks.

In another aspect, an apparatus is provided. The apparatus includes: means for determining a search space for hydrogen bond networks related to one or more molecules, where the search space includes a plurality of energy terms related to a plurality of residues related to the hydrogen bond networks; means for searching the search space to identify one to or more hydrogen bond networks based on the plurality of energy terms; means for screening the identified one or more hydrogen bond networks to identify one or more screened hydrogen bond networks based on scores for the one or more identified hydrogen bond networks; and means for generating an output related to the one or more screened hydrogen bond networks.

In one aspect, the invention provides polypeptides comprising an amino acid sequence that is at least 75% identical over its full length to the amino acid sequence selected from the group consisting of SEQ ID NOS:2-79.

In another aspect, the invention provides polypeptides comprising or consisting of the amino acid sequence of Formula I: Z1-Z2-Z3-Z4-Z5, wherein:

Z1 is a helix initiating sequence comprising the amino acid sequence of Formula 2: J1-J2-J3, wherein

-   -   J1 is selected from the group consisting of S, T, N, and D;     -   J2 is selected from the group consisting of P, E, R, K, L, A;         and     -   J3 is selected from the group consisting of E, D, R, K, I, L, V,         A, S, T, Y, or is absent;

Z3 is a helix connecting sequence having the amino acid sequence of Formula 3:

(SEQ ID NO: 1) [RKED]-L-[NQEDRKST]-[NQEDRKST]-[NQEDRKST]-G- [STNQED]-[STNQED]-[STND]-E-[EDRK]-V-[RKED];

Z5 is a helix terminating sequence comprising the amino acid sequence of Formula 4:

xx-xx-[RKEDSTNQYA];

Z2 is selected from the group consisting of general formulae BX₁BX₂, X₁BBX₂, X₁BX₂B, X₁X₂B, BX₁X₂B, and BBX₁X₂, wherein:

-   -   B is xx-S-L-xx-xx-Q-xx;     -   X₁ and X₂ independently have the amino acid sequence of Formula         5:         O₁O₂O₃O₄O₅O₆O₇ wherein:         -   O₁, O₄, O₅, and O₇ are xx;         -   O₂ and O₃ are independently selected from the group             consisting of I, L, and A; and         -   O₆ is L; and     -   Z4 is selected from the group consisting of general formulae         B₂X₃B₂X₄, X₃B₂B₂X₄, X₃B₂X₄B₂, X₃X₄B₂B₂, B₂X₃X₄B₂, and B₂B₂X₃X₄,         wherein         -   B₂ is xx-L-A-xx-xx-Q-xx; and         -   X₃ and X₄ independently have the amino acid sequence of             Formula 6:             O₁₀O₁₁O₁₂O₁₃O₁₄O₁₅O₁₆ wherein             -   O₁₀, O₁₃, O₁₄, and O₁₆ are xx             -   O₁₁ is L, and             -   O₁₂ and O₁₅ are independently selected from the group                 consisting of I, L, V, and A;     -   wherein xx is any amino acid, and     -   wherein:     -   (i) when Z2 is BX₁BX₂ then Z4 is X₃B₂X₄B₂;     -   (ii) when Z2 is X₁BBX₂ then Z4 is X₃B₂B₂X₄;     -   (iii) when Z2 is X₁BX₂B then Z4 is B₂X₃B₂X₄;     -   (iv) when Z2 is X₁X₂BB then Z4 is B₂X₃X₄B₂;     -   (v) when Z2 is BX₁X₂B then Z4 is B₂X₃X₄B₂; and     -   (vi) when Z2 is BBX₁X₂ then Z4 is X₃X₄B₂B₂.

In other aspects, the invention provides nucleic acids that encode the polypeptides of the invention, expression vectors comprising the nucleic acids of the invention operatively linked to a promoter sequence, and host cells comprising the expression vectors.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1. Overview of the HBNet™ method and design strategy. (A) (left) All sidechain conformations (rotamers) of polar amino acid types considered for design at each residue position; (middle) many combinations of hydrogen-bonding rotamers are possible and the challenge is to traverse this space and extract (right) networks of connected hydrogen bonds. (B-D) HBNet™. (B) HBNet™ precomputes the hydrogen bond and steric repulsive interaction energies between sidechain rotamers at all pairs of positions and stores them in a graph structure; nodes are residue positions, residue pairs close enough to interact are connected by edges, and for each edge there is an interaction energy matrix; yellow indicates rotamer pairs with energies below a specified threshold (hydrogen bonds with good geometry and little steric repulsion). Traversing the graph elucidates all possible connectivities of hydrogen bonding rotamers (networks) that do not clash with each other. In the simple example shown, two pairs of sidechain rotamers at Res_(i) and Res_(j) make good-geometry hydrogen bonds, but graph traversal shows that only one of these (left) can be extended into a connected network: (C) Res_(i) rotamer 3 (i:3) can also hydrogen bond to Res_(k) rotamer 2 (k:2) and Res_(j) rotamer 4 (!:4), yielding a “good” network of fully connected Asn residues with all heavy-atom donors and acceptors satisfied, whereas (D) would be rejected because the hydrogen-bonding rotamers i:6 (Gln) and j:4 (Ser) cannot form additional hydrogen bonds to nearby positions k and l, leaving unsatisfied buried polar atoms. (E-G) Design strategy: (E) Parametric backbone generation of two-ring coiled coils: a C3 symmetric trimer is shown, colored by monomer subunit labeled with parameters sampled: supercoil radius of inner (R_(in)) and outer (R_(out)) helices, helical phase of the inner (Δφ_(1 in)) and outer (Δφ_(1 out)) helices, supercoil phase of the outer helix (11cp0), z-offset between the inner and outer helices (Z_(off)), and the supercoil twist (ω₀). (F) HBNet™ is applied to parametric backbones to identify the best hydrogen bond networks. (G) Networks are maintained while remaining residue positions are designed in context of the assembled symmetric oligomer.

FIG. 2. The outer ring of helices increase thermostability and can overcome poor helical propensity of the inner helices. (A) CD spectrum (260-195 nm) of design 2L4HC2_23 at 25° C. (blue), 75° C. (red), 95° C. (green), and 25° C. after cooling (purple). (B) 2L4HC2_23, denaturation by GdmCl monitoring 222 nm; (C) 2L4HC2_9, a supercoiled C2 homodimer colored by chain, looking down the supercoil axis. (D) CD spectrum of 2L4HC2_9 as in (A). (E) Inner ring design of 2L4HC2_9. (F) CD temperature melt monitoring absorption at 222 nm; 2L4HC2_9 (black) is significantly more stable than 2L4HC2_9_inner (gray). (G) 2L6HC3_13, a supercoiled C3 homotrimer. (H) CD spectrum of 2L6HC3_13 at different temperatures as in (A). (I) 2L6HC3_13_inner. (3) CD spectrum of 2L6HC3_13 (black) versus 2L6HC3_13_inner (gray) shows that the inner helix by itself is primarily unfolded. All CD data is plotted in Mean Residue Ellipticity (MRE) 10³ deg cm² dmol⁻¹

FIG. 3. Structural characterization by x-ray crystallography. (A-F) Crystal structures (white) are superimposed onto the design models for six different topologies; (left) the full backbone is shown with cross-sections corresponding to the (middle) designed hydrogen bond networks; panel outline color corresponds to cross-section color on the left; RMSD over all network residue heavy-atoms is reported inside each panel. (A) 2L6HC3_13 (1.64 Å resolution; RMSD=0.51 Å over all Cα atoms) and (B) 2L6HC3_6 (2.26 Å resolution; RMSD=0.77 Å over all Cα atoms) are left-handed C3 homotrimers, each with two identical networks at different locations that span the entire interface, contacting all six helices. (C) 2L8HC4_12, a left-handed C4 homotetramer with two different hydrogen bond networks; the low (3.8 Å) resolution does not allow assessment of the hydrogen bond network sidechains. (D) 2L4HC2_9 (2.56 Å resolution; 0.39 Å RMSD over all Cα atoms) and (E) 2L4HC2_23 (1.54 Å resolution; RMSD=1.16 Å over all Cα atoms) are left-handed C2 homodimers, each with one network. (F) 5L6HC3_1 (2.36 Å resolution; RMSD=0.51 Å over all Cα atoms) is a C3 homotrimer with straight, untwisted helices and two identical networks at different cross-sections. (G, H) Schematics of hydrogen bond networks from 2L6HC3_13 (A) and 5L6HC3_1 (F). The indicated hydrogen bonds are present in both design model and crystal structure.

FIG. 4 Structural characterization by small angle x-ray scattering (SAXS). (left) backbones and (middle) h-bond networks for the design models are displayed as in FIG. 3; (right) design models were fit to experimental scattering data (black) using FoXS; Chi2 values of fit (X) indicated inside each panel. (A) 5L8HC4_6 (X=1.36), an untwisted C4 homotetramer with two identical h-bond networks. (B) 5L4HC2_12 (X=1.45), an untwisted C2 homodimer with a single h-bond network. (C) 3L6HC2_4 (X=2.04), a parallel right-handed C2 homodimer with two repeated networks and two inner helices, one outer helix. (D) 2L6Hanti_3 (X=1.80), a left-handed anti parallel homodimer with two inner helices, one outer helix; because of the anti-parallel geometry, the same network occurs in two locations.

FIG. 5. The hydrogen bond networks confer specificity. (A) Interaction surfaces of monomer subunits for six structurally verified designs, ordered by increasing contiguous hydrophobic interface area, as calculated by h-patch; hydrogen bond network residues are colored. (B) Binding heat-map from yeast two-hybrid assay. Designs in (A) were fused to both DNA-binding domain and Activation domain constructs and binding measured by determining the cell growth rate (maximum ΔOD/hour): darker cells indicate more rapid growth, hence stronger binding; values are the average of at least 3 biological replicates. The heat-map is ordered as in (A), and designs with more extensive networks and better-partitioned hydrophobic interface area exhibit higher interaction specificity. (C-G) Modular networks confer specificity in a programmable fashion. (C) The backbone corresponding to designs 2L6HC3_13 (FIG. 3A) and 2L6HC3_6 (FIG. 3B) can accommodate different networks at each of four repeating geometric cross-sections. (D) Three possibilities for each cross-section: Network “A”, Network “B”, or hydrophobic, “X”. (E) Combinatorial designs using this three letter “alphabet” were tested for interaction specificity using the yeast two-hybrid assay as in (B). Axis labels denote the network pattern; for example, “AXBX” indicates Network A at cross-section 1, Network B at cross-section 3, and X (hydrophobic) at the two others. (F) SAXS profiles for combinatorial designs as in FIG. 4; (G) SEC chromatograms and estimated molecular weights (from MALS); designs range from ˜27-30 kDa. AAXX, XXBB, and XXXX correspond to designs 2L6HC3_13, 2L6HC3_6, and 2L6HC3_hydrophobic_1, respectively.

FIG. 6 is a block diagram of an example computing network, in accordance with an example embodiment.

FIG. 7A is a block diagram of an example computing device, in accordance with an example embodiment.

FIG. 7B depicts a network of computing devices arranged as a cloud-based server system, in accordance with an example embodiment.

FIG. 8 is a flowchart of a method, in accordance with an example embodiment.

DETAILED DESCRIPTION OF THE INVENTION

All references cited are herein incorporated by reference in their entirety. Within this application, unless otherwise stated, the techniques utilized may be found in any of several well-known references such as: Molecular Cloning: A Laboratory Manual (Sambrook, et al., 1989, Cold Spring Harbor Laboratory Press), Gene Expression Technology (Methods in Enzymology, Vol. 185, edited by D. Goeddel, 1991. Academic Press, San Diego, Calif.), “Guide to Protein Purification” in Methods in Enzymology (M. P. Deutshcer, ed., (1990) Academic Press, Inc.); PCR Protocols: A Guide to Methods and Applications (Innis, et al. 1990. Academic Press, San Diego, Calif.), Culture of Animal Cells: A Manual of Basic Technique, 2^(nd) Ed. (R. I. Freshney. 1987. Liss, Inc. New York, N.Y.), Gene Transfer and Expression Protocols, pp. 109-128, ed. E. J. Murray, The Humana Press Inc., Clifton, N.J.), and the Ambion 1998 Catalog (Ambion, Austin, Tex.).

As used herein, the singular forms “a”, “an” and “the” include plural referents unless the context clearly dictates otherwise. “And” as used herein is interchangeably used with “or” unless expressly stated otherwise.

As used herein, the amino acid residues are abbreviated as follows: alanine (Ala; A), asparagine (Asn; N), aspartic acid (Asp; D), arginine (Arg; R), cysteine (Cys; C), glutamic acid (Glu; E), glutamine (Gln; Q), glycine (Gly; G), histidine (His; H), isoleucine (Ile; I), leucine (Leu; L), lysine (Lys K), methionine (Met; M), phenylalanine (Phe; F), proline (Pro; P), serine (Ser, S), threonine (Thr; T), tryptophan (Trp; W), tyrosine (Tyr, Y), and valine (Val; V).

All embodiments of any aspect of the invention can be used in combination, unless the context clearly dictates otherwise.

In one aspect, the invention provides polypeptides comprising an amino acid sequence that is at least 75% identical over its full length to the amino acid sequence selected from the group consisting of SEQ ID NOS:2-79.

AXAX (SEQ ID NO: 2) TRTRSLREQEEIIRELERSLREQEELLRELERLQREGSSDEDVRE LLREIKKLAREQKYLVEELKKLAREQKRQD; XAAX (SEQ ID NO: 3) TRTEIIRELERSLREQERSLREQEELLRELERLQREGSSDEDVRE LLREIKKLAREQKKLAREQKYLVEELKRQD; XAXA (SEQ ID NO: 4) TRTEIIRELERSLREQEELAKRLKRSLREQERLQREGSSDEDVRK LAREQKELVEEIEKLAREQKYLVEELKRQD; and XXAA (SEQ ID NO: 5) TRTEIIRELEELAKRLKRSLREQERSLREQERLQREGSSDEDVRK LAREQKKLAREQKELVEEIEYLVEELKRQD

Polypeptide Nomenclature:

The name of the polypeptides shown below indicates oligomerization state and topology, and sequences below are organized by topology and oligomerization state. The first two characters indicate supcrcoil geometry: ‘2L’ refers to a two-layer heptad repeat that results in a left-handed supercoil; ‘3L’ refers to a three-layer 11-residue repeat with a right-handed supercoil; and ‘5L’ refers to untwisted designs with a five-layer 18-residue repeat and straight helices (no supercoiling), where “layer” in this context is the number of unique repeating geometric slices, or layers, along the supcrcoil axis. The middle two characters indicate the total number of helices, and the final two indicate symmetry. Thus. “2L6HC3” denotes a left-handed, six-helix trimer with C3 symmetry. Underlined residues are optional.

2L8HC4_12 (SEQ ID NO: 6) GTAIEANSRMLKALIEIAKAIWKALWANSLLLEATSRGDTERMRQ WAEEAREIYKEAKKIIDEADEIVKEAKERHD 5L6HC3_1 (SEQ ID NO: 7) SEELRAVADLQRLNIELARKLLEAVARLQELNIDLVRKTSELTDE KTIREEIRKVKEESKRIVEEAEEEIRRAKEESRYIADESRGS 2L4HC2_9 (SEQ ID NO: 8) GTSDYIIEQIQRDQEEARKKVEEAEERLERVKEASKRGVSSDQLL DLIRELAEIIEELIRIIRRSNEAIKELIKNQS 2L4HC2_11 (SEQ ID NO: 9) GSEDYKLREAQRELDKQRKDTEEIRKRLKEIQRLTDERTSTADEL IKELREIIRRLQEQSEKLREIIEELEKIIRKR 2L4HC2_23 (SEQ ID NO: 10) GTRTEIIRELERSLREQEELAKRLKELLRELERLQREGSSDEDVR ELLREIKELVEEIEKLAREQKYLVEELKRQD  2L4HC2_24 (SEQ ID NO: 11) GTDTDELLRLAKEQAELLKEIKKLVEEIARLVKEIQEDPSDELLK TLAELVRKLKELVEDMERSMKEQLYIIKKQKS 5L8HC4_6 (SEQ ID NO: 12) GSKDTEDSRKIWEDIRRLLEEARKNSEEIWKEITKNPDTSEIARL LSEQLLEIAEMLVRIAELLSRQTEQR 2L6HC3_AXAX (SEQ ID NO: 13) GTKYEIREALKEAQKQLEDLKRMLDELRRNLEELKRNPSEDALVE NNELIVRVLEVIVENNRSIIEILKLLAKSD 2L6HC3_AXBX (SEQ ID NO: 14) GTKYKIREMLEEAKRSLEELRRILEKLKESLRELRRNPSEDALVN NNEVIVKAIEASVENQRIIIELARMLAESD 2L6HC3_AXXB (SEQ ID NO: 15) GTKYRIKDTLRELKRALEELKKILEELQRSLEELRRNPSEDALVN NNEVIVKAIEAAVRAIEISAENQRMLAESD 2L6HC3_XAAA (SEQ ID NO: 16) GTKYEARKQLEEMKKQLKRSLERLREILERLEENPSEDVIVEAIR AIVENNKQIVENNRSIIENNETIIRSD 2L6HC3_XBXA (SEQ ID NO: 17) GTKYELRRQLEELEKLLRELRKSLDELRKILEELERNPSEDVIVR AIKASVKNQEIIVEVLRAIIENNKTIAKSD 2L6HC3_12 (SEQ ID NO: 18) GTKYELRRALEELEKALQELREMLRKLKESLEELKKNPSEDALVR NNELIVEVLRVIVEVLSIIARVLEINARSD 2L6HC3_13 (SEQ ID NO: 19) GTKYELRRALEELEKALRELKKSLDELERSLEELEKNPSEDALVE NNRLNVENNKIIVEVLRIIAEVLKINAKSD 2L6HC3_6 (SEQ ID NO: 20) GTKYKIKETLKRLEDSLRELRRILEELKEMLERLEKNPDKDVIVE VLKVIVKAIEASVENQRISAENQKALAESD 2L6HC3_10 (SEQ ID NO: 21) GTKYEIKKALKELEEAIQKLKKSLKELKESLKELQKNPSEDALVK NNSLNVANNEIIVEVLEIIARILELLARSD 2L6HC3_11 (SEQ ID NO: 22) GTKYEIKEALRELNRALKELKEALRELERSLRELQKNPDKDALVR NNELNVDVARIIVEVLSIIARVLELLAKSD 2L6HC3_12 (SEQ ID NO: 23) GTKYELRRALEELEKALQELREMLRKLKESLEELKKNPSEDALVR NNELIVEVLRVIVEVLSIIARVLEINARSD 2L6HC3_13 (SEQ ID NO: 24) GTKYELRRALEELEKALRELKKSLDELERSLEELEKNPSEDALVE NNRLNVENNKIIVEVLRIIAEVLKINAKSD 2L6HC3_14 (SEQ ID NO: 25) GTKYELREAIRKLEEALRKLKKALDELRKSLEELKKNPSEDALVR NNELNVKVAEIIVKVLKIIAEAIKINAKSD 2L6HC3_19 (SEQ ID NO: 26) GTEEYKLRELLKRHNEVLKELQKAAKEAEEVAERFKKTNDITEAI RVIADLLRAIVKAIETNSRVVKMIVELNE 2L6HC3_2 (SEQ ID NO: 27) GTKYIEKLLREAQRTLEELKRLLEELKEMLKELERANATDARLIA EVIRVIVEVLRASVENQEMIIRILKAITEE 2L6HC3_23 (SEQ ID NO: 28) TEKDVLRIIVKNNEIIVKVLSVIAEVLKIIAKILENPSEYMLKEL KKALKELEKMLKELRKSLKELKEALRELEGS 2L6HC3_37 (SEQ ID NO: 29) GTLDYKLDEMLKKLEKSREEMEKMAQELRRALEELEKNSNVDKVL KIIIKAIQLSIENQKLNLEAVRLLIEAQKS 2L6HC3_6 (SEQ ID NO: 30) GTKYKIKETLKRLEDSLRELRRILEELKEMLERLEKNPDKDVIVE VLKVIVKAIEASVENQRISAENQKALAESD 2L8HC4_3 (SEQ ID NO: 31) GTDEYKWKEEVRRFEEEAKKWEEELKEMRKRIEDAKKGRPTLKVN LEAAEALLEAARLIVEAAKLLLAAAKLNEKQN 2L8HC4_9 (SEQ ID NO: 32) GSDEDRKAKELIERQRKLTDEAEEWAKQNEEIAKKIEKQPDTSLV ARMLANVSRMLLATNRALLANTEALEALIRKT 2L8HC4_12 (SEQ ID NO: 33) GTAIEANSRMLKALIEIAKAIWKALWANSLLLEATSRGDTERMRQ WAEEAREIYKEAKKIIDEADEIVKEAKERHD 3L6HC2_4 (SEQ ID NO: 34) SALEKIAKLIIEAARLSAELARRAARASAEMARKAIEAVSEERGS ESLLKIVADLIVESQEAVVRLIIESQQIAAKLAEDLIRAAKEAAS DESKMEEVAKEVQERAERAARDIERKLKRVLEELDYKLKESRDGS 3L6HC2_6 (SEQ ID NO: 35) TALEIAVRLNREAAREAARENADTARKAARRIAEVAKRLAEENRD AKLAARLLAEIARLLAELIARQSELLAEWLATQSKLAAELARKDT SATDEAERIRKESEELLDKVREEIKRLEDEVSKTIEELSERVRGS 3L6HC2_7 (SEQ ID NO: 36) SILELAHESNRRALEMASRANREAMKAAREMIRAASEAARRAGSS NDKDSLRMIEEALRLALRMIEETNKKAVRMVLENNRKMVEAEKKK LSEEEIKRIAKETEDRMREIARRASEEARRLAEEIKREADYRSGS 5L6HC3_1 (SEQ ID NO: 37) SEELRAVADLQRLNIELARKLLEAVARLQELNIDLVRKTSELTDE KTIREEIRKVKEESKRIVEEAEEEIRRAKEESRYIADESRGS 5L6HC3_3 (SEQ ID NO: 38) GTERKDRLRKELKRIAEETDKWVEELKEELERILRTIEELRKDPS SEVIVDIARIQLEALREVIRVVAENSKAILEAIHRVIEEG 5L6HC3_5 (SEQ ID NO: 39) SKEVRLQKLNAEIMKEIMELIIRLQEANARIIEELVRLIIDLERS TDSKRMIEEIRKVAERAIEESKRLLEEAEKAMRRAIYESEDALRE GS 5L8HC4_1 (SEQ ID NO: 40) GSKVEELLRKSEEAAERAKRELERLLEESERIVAEAQALAEKYES QKVWVRILIELIRATNRMLAEIARILLEMIEVTNRMIAESTK 5L8HC4_2 (SEQ ID NO: 41) SEQLKEIARILIKLIESLTRFILEVARILIELIEETQRLIVASTD SDESELERIARESKKKAKKALDELKKIVDDQRREAKKAIEELEYD GS 5L8HC4_6 (SEQ ID NO: 42) GSKDTEDSRKIWEDIRRLLEEARKNSEEIWKEITKNPDTSEIARL LSEQLLEIAEMLVRIAELLSRQTEQR 2L4HC2_1 (SEQ ID NO: 43) GTAYELLRKAEELEKKQQELLKRQEELAKTAEELRKKGGNADSMM KIIKESTRIVRESTEIVKELLKIIRELRRQS 2L4HC2_5 (SEQ ID NO: 44) GTRTEYLKKLAEEAKELAKRSRELSKESRRLSEEARRDPDKEKLL RVVKKLQEVIEELQRVIEELLRVIKEALENQS 2L4HC2_6 (SEQ ID NO: 45) GTETEYQRELAREARRLAKRSRELSERSRKLSEDAKRDPDKDKLL EVVERLQQVIEELQKVIEELLRVIESSLKTIS 2L4HC2_9 (SEQ ID NO: 46) GTSDYIIEQIQRDQEEARKKVEEAEERLERVKEASKRGVSSDQLL DLIRELAEIIEELIRIIRRSNEAIKELIKNQS 2L4HC2_10 (SEQ ID NO: 47) GTEEYRRKEQEERTKEQQERTERQRRKTEELKRATKEGTLTPEEA IRQAQKQSENAERQSREAEKQSREANEALRKR 2L4HC2_11 (SEQ ID NO: 48) GSEDYKLREAQRELDKQRKDTEEIRKRLKEIQRLTDERTSTADEL IKELREIIRRLQEQSEKLREIIEELEKIIRKR 2L4HC2_12 (SEQ ID NO: 49) GSEDYKLKELQKRNKKQEEEAKRNDDERKKIEELTRKRTSTADEL IRELQRSNEEMQRSQREMQDQSRRLEDIIRKR 2L4HC2_14 (SEQ ID NO: 50) GTEDYKRREAERKLQKQQEELKELKRKLEEIRELHEKGVGSPDRL IRELERIIRELQRMQKENEKIIKELQRIIKKR 2L4HC2_18 (SEQ ID NO: 51) GTESKYLLEEARRLKDEARKLKEEAKKVKEESRKLIERIDRGEDS DRELLERLKEQNNRLLEIIERLLEIIERLLKLIEEWTRDS 2L4HC2_19 (SEQ ID NO: 52) GTEEDYAEREIRKMKEEQKRQRKRLEELERELQEMQEKKREGTSD AKEVIDQLERIIRELQEIIRSQEDITRKLEEIIRRMKENS 2L4HC2_20 (SEQ ID NO: 53) GTNKEELKRTMEEQQRILEKLLRTIKEQKEILRKQEEGRATKEEL KRLTKLAQEQERMMRELIDLARKQAYLLKRES 2L4HC2_21 (SEQ ID NO: 54) GTREEKIRRILEEIQKIMEEIKRIMEEIKRTQEEAEKHGSSKKAI EKQKELLRRLEELLRKLERLLRELEYLMRDEK 2L4HC2_22 (SEQ ID NO: 55) GTREEWLYRILELIERIERLIKEIIRLSRRALELLENNASNEEWA QEIKEMQRKIQEWLKQILEWLKKIKEWIRESQ 2L4HC2_23 (SEQ ID NO: 56) GTRTEIIRELERSLREQEELAKRLKELLRELERLQREGSSDEDVR ELLREIKELVEEIEKLAREQKYLVEELKRQD 2L4HC2_24 (SEQ ID NO: 57) GTDTDELLRLAKEQAELLKEIKKLVEEIARLVKEIQEDPSDELLK TLAELVRKLKELVEDMERSMKEQLYIIKKQKS 5L4HC2_1 (SEQ ID NO: 58) GTEETKNSKRVLDIIEELMRQVEENSRELEKRIKELLRQTKEGKT KKELERDVRRTIEEQKKELRRLKEQVRKTKEEQREEQYRS 5L4HC2_2 (SEQ ID NO: 59) GTRTEKLMKEVEEIQRRQIELLKKLMKEVEDSSKRNQEATERGTT KKKWKEEQEKILEDLKREVRRIIEESRKWLEDLKKKVYES 5L4HC2_3 (SEQ ID NO: 60) GTEKYRLREEVRRTIEEQKENLERLKQEVKETERKTEEWRERNTT TEDAQREQIKIIRRLMKEVERNSRRLEKELRRLVEETRES 5L4HC2_6 (SEQ ID NO: 61) GTEKYRLIRESERALRELKRKVRELEEDQRERLDEQRKKVEEGQT TDELLRQNEENSRRMLKETKKLLREIERIQREQQRQNQEN 5L4HC2_7 (SEQ ID NO: 62) GTEKEKEIEKNSREVIKQVEDILREIKENSKRNIEIIKELQKDPS DEKMRETIEQQRENLERLERKARELIRRQERNLRETQYKD 5L4HC2_9 (SEQ ID NO: 63) GTEKYRIIEEQRRNLEDLEREIREIIKKLKEALERLRELVERNST NDRLLDEVRKIIEEAIEDMKRLLEKVERSIRQNIEELRRS 5L4HC2_10 (SEQ ID NO: 64) GTNKEYLRRKVKELKDQQKRNLEELEREVRRLIKEIEEWRERNTT TDRALKEIIRQIQRLLEEARRNSEEVLRQIEEIMEETRES 5L4HC2_11 (SEQ ID NO: 65) GTEEERAERIIRAIRELMREVERNSKEVLQWIKEMLRLTKENSST KELEERWREIEERQRRNLEKLKEEVRRLEDEIRQETYRS 5L4HC2_12 (SEQ ID NO: 66) GTETKKLVEEVERALRELLKTSEDLVRKVEKALRELLELIRRGGT KDKIEEKIRRVLEEIKRELERQKRKIEDVLRQIKEELYRS 2L6Hanti_1 (SEQ ID NO: 67) SDYLRLATEHNKLAVEANRLAIELAKSAVELAETDPSKTALEHAE LAARLLEMMVQFTKAAQELTREAIRKEGRNEESEKVLRKSKEAYK ESEKALEDARRLLDELRKKGS 2L6Hanti_2 (SEQ ID NO: 68) SEELRKAAENNELAVRLAEAALRMARSALHLFEENPSDEMLKFLE LAMEVAKMAAELLKASLKMLKKAAEERGSDESVKYLADKSRDIMR QITEELKKLEEEAKRAQKRGS 2L6Hanti_3 (SEQ ID NO: 69) SEKARIAVENLEAALRLNRAAAEMQKSAIKIMDDNRSDEKALRYL RLTTKVLRMSVELLRASLELAEKALREEGSDDSAEKVRKEAEEIL KESTEILKEADKETKRADEEGS 2L6Hanti_4 (SEQ ID NO: 70) SRRLELAARINKAAAENARSAIEIQELAARLADELSSSKKVIDFA RATTEVLRMSVKLLKLSLEMLEEAARQDGRSEEVRYLAEESKKIL EEARKALEDADRLTKRIEEEGS 2L6Hanti_5 (SEQ ID NO: 71) TDVLRIAAENLKAAVELAKAALEMAKSAIEIAKTLTEDDEALKFA RAAAEVLRMAAKLLKLSIELARKAAEEEGSDDEVRYILDEARKQA DELREALKKVDEIMKELDKRGS 5H2LD_10 (SEQ ID NO: 72) TRRKQEMKRLKYEMEKIREETEEVKKEIEESKKRPQSESAKNLIL IMQLLINQIRLLALQIRMLALQLQE 5H2LD_13 (SEQ ID NO: 73) TEDQERLRKQMEYERKHTEKVEKEIRKVEQKMKSHEDTSLRLLVL LIARLLINQIRLLILQIRSLSNLERN 5H2LD_15 (SEQ ID NO: 74) TESTLLILIMRLLVQQSELLQLQIQMLQLLLKANNGTNKTEIERR SKEMEEELKRMKESNREMTKRIKEME 5H2LD_18 (SEQ ID NO: 75) TESDLLRQISKLLIIQIRLLLLQIQMLILLLKMNTGTNTTQITKE AKRIEKEAQEARKELEKMQESNKKQT 6H2LD_8 (SEQ ID NO: 76) TEDEIRKLRKLLEEAEKKLYKLEDKTRRSEEISKTDDDPKAQSLQ LIAESLMLIAESLLIIAISLLLSSRNG 7H2LD_3 (SEQ ID NO: 77) TEDEELQRVEEEIRELERKAKELHYKSEEIRKKVNGRSPQAEALL MIAQALLNISESLLAIAKALLMIARST 8H2LD_4 (SEQ ID NO: 78) TDEREIIKRVKRLLEEVEYLIERLRDQIEKAEKGLLDSRKAQQNA EALVNLIKAMVLVLKALLLAKELER 8H2LD_4_KE (SEQ ID NO: 79) TEEQYIIEEVKKLLEEVKKLIEELKKQIEKAEKGEEDSRKAQQNA EALVNLIKAMVLVLKALLLAKELER

The polypeptides of this aspect of the invention have been shown in the examples that follow to be capable of forming homo-oligomers with modular hydrogen bond network-mediated specificity. In various embodiments, the polypeptides comprise or consist of an amino acid sequence that is at least 75%, 80%, 85%, 90%, 91%, 92%, 93%, 94%, 95%, 96%, 97%, 98%, 99%, or 100% identical over its full length to the amino acid sequence selected from the group consisting of SEQ ID NOS:2-79.

As used throughout the present application, the term “polypeptide” is used in its broadest sense to refer to a sequence of subunit amino acids. The polypeptides of the invention may comprise L-amino acids, D-amino acids (which are resistant to L-amino acid-specific proteases in vivo), or a combination of D- and L-amino acids. The polypeptides described herein may be chemically synthesized or recombinantly expressed. The polypeptides may be linked to other compounds to promote an increased half-life in vivo, such as by PEGylation, HESylation, PASylation, glycosylation, or may be produced as an Fc-fusion or in deimmunized variants. Such linkage can be covalent or non-covalent as is understood by those of skill in the art.

As will be understood by those of skill in the art, the polypeptides of the invention may include additional residues at the N-terminus, C-terminus, or both that are not present in the polypeptides of the invention; these additional residues are not included in determining the percent identity of the polypeptides of the invention relative to the reference polypeptide.

In one embodiment, changes from the reference polypeptide are conservative amino acid substitutions. As used herein, “conservative amino acid substitution” means an amino acid substitution that does not alter or substantially alter polypeptide function or other characteristics. A given amino acid can be replaced by a residue having similar physiochemical characteristics, e.g., substituting one aliphatic residue for another (such as Ile, Val, Leu, or Ala for one another), or substitution of one polar residue for another (such as between Lys and Arg; Glu and Asp; or Gln and Asn). Other such conservative substitutions, e.g., substitutions of entire regions having similar hydrophobicity characteristics, are well known. Polypeptides comprising conservative amino acid substitutions can be tested in any one of the assays described herein to confirm that a desired activity, e.g. antigen-binding activity and specificity of a native or reference polypeptide is retained.

Amino acids can be grouped according to similarities in the properties of their side chains (in A. L. Lehninger, in Biochemistry, second ed., pp. 73-75, Worth Publishers, New York (1975)): (1) non-polar: Ala (A), Val (V), Leu (L), Ile (I), Pro (P), Phe (F), Trp (W), Met (M); (2) uncharged polar: Gly (G), Ser (S), Thr (T), Cys (C), Tyr (Y), Asn (N), Gln (Q); (3) acidic: Asp (D), Glu (E); (4) basic: Lys (K), Arg (R), His (H). Alternatively, naturally occurring residues can be divided into groups based on common side-chain properties: (1) hydrophobic: Norleucine, Met, Ala, Val, Leu, Ile; (2) neutral hydrophilic: Cys, Ser, Thr, Asn, Gln; (3) acidic: Asp, Glu; (4) basic: His, Lys, Arg; (5) residues that influence chain orientation: Gly, Pro; (6) aromatic: Trp, Tyr, Phe. Non-conservative substitutions will entail exchanging a member of one of these classes for another class. Particular conservative substitutions include, for example; Ala into Gly or into Ser, Arg into Lys; Asn into Gln or into H is; Asp into Glu; Cys into Ser; Gln into Asn; Glu into Asp; Gly into Ala or into Pro; His into Asn or into Gln; Ile into Leu or into Val; Leu into Ile or into Val; Lys into Arg, into Gln or into Glu; Met into Leu, into Tyr or into Ile; Phe into Met, into Leu or into Tyr; Ser into Thr; Thr into Ser; Trp into Tyr; Tyr into Trp; and/or Phe into Val, into Ile or into Leu.

As noted above, the polypeptides of the invention may include additional residues at the N-terminus, C-terminus, or both. Such residues may be any residues suitable for an intended use, including but not limited to detection tags (i.e.: fluorescent proteins, antibody epitope tags, etc.), linkers, ligands suitable for purposes of purification (His tags, etc.), and peptide domains that add functionality to the polypeptides.

In another aspect, the invention provides polypeptides comprising or consisting of the amino acid sequence of Formula I: Z1-Z2-Z3-Z4-Z5, wherein:

Z1 is a helix initiating sequence comprising the amino acid sequence of Formula 2: J1-J2-J3, wherein

-   -   J1 is selected from the group consisting of S. T, N, and D;     -   J2 is selected from the group consisting of P, E, R, K, L, A;         and     -   J3 is selected from the group consisting of E, D, R, K, I, L, V,         A, S, T, Y, or is absent;

Z3 is a helix connecting sequence having the amino acid sequence of Formula 3:

(SEQ ID NO: 1) [RKED]-L-[NQEDRKST]-[NQEDRKST]-[NQEDRKST]-G- [STNQED]-[STNQED]-[STND]-E-[EDRK]-V-[RKED]; 

Z5 is a helix terminating sequence comprising the amino acid sequence of Formula 4:

xx-xx-[RKEDSTNQYA];

Z2 is selected from the group consisting of general formulae BX₁BX₂, X₁BBX₂, X₁BX₂B, X₁X₂BB, BX₁X₂B, and BBX₁X₂, wherein:

-   -   B is xx-S-L-xx-xx-Q-xx;     -   X₁ and X₂ independently have the amino acid sequence of Formula         5:         O₁O₂O₃O₁O₅O₅O₇ wherein:         -   O₁, O₄, O₅, and O₇ are xx;         -   O₂ and O₃ are independently selected from the group             consisting of L, and A; and         -   O₆ is L; and

Z4 is selected from the group consisting of general formulae B₂X₃B₂X₄, X₃B₂B₂X₄, X₃B₂X₄B₂, X₃X₄B₂B₂, B₃X₃X₄B₂, and B₂B₂X₃X₄, wherein

-   -   B₂ is xx-L-A-xx-xx-Q-xx; and     -   X₃ and X₄ independently have the amino acid sequence of Formula         6:         O₁₀O₁₁O₁₂O₁₃O₁₄O₁₅O₁₆ wherein         -   -   O₁₀, O₁₃, O₁₄, and O₁₆ are xx             -   O₁₁ is L, and             -   O₁₂ and O₁₅ are independently selected from the group                 consisting of I L, V, and A;

wherein xx is any amino acid, and

wherein:

(i) when Z2 is BX₁BX₂ then Z4 is X₃B₂X₄B₂;

(ii) when Z2 is X₁BBX₂ then Z4 is X₃B₂B₂X₄;

(iii) when Z2 is X₁BX₂B then Z4 is B₂X₃B₂X₄;

(iv) when Z2 is X₁X₂BB then Z4 is B₂B₂X₃X₄;

(v) when Z2 is BX₁X₂B then Z4 is B₂X₃X₄B₂; and

(vi) when Z2 is BBX₁X₂ then Z4 is X₃X₄B₂B₂.

The polypeptides of this aspect of the invention have been shown in the examples that follow to be capable of forming homo-oligomers with modular hydrogen bond network-mediated specificity.

In one embodiment, J3 is present. In another embodiment, Z1 is TRT. In a further embodiment, Z3 is RLQREGSSDEDVR (SEQ ID NO: 81). In a still further embodiment, Z5 is RQD. In another embodiment, B is RSLREQE (SEQ ID NO: 82). In a further embodiment, O₁, O₄, O₅, and O₇ are independently selected from the group consisting of E, R, and K. In a still further embodiment, X₁ and X₂ are independently selected from the group consisting of EIIRELE (SEQ ID NO: 83), ELLRELE (SEQ ID NO: 84), and ELAKRLK (SEQ ID NO: 85). In another embodiment, B₂ is KLAREQK (SEQ ID NO: 86). In one embodiment, O₁₂ and O₁₅ are independently selected from the group consisting of I, L, V, and A. In another embodiment, X₃ and X₄ are independently selected from the group consisting of [YE]-LVEELK (SEQ ID NO: 87), [YE]-LLREIK (SEQ ID NO: 88), and [YE]-LVEEIE (SEQ ID NO: 89). As used herein, residues in brackets are alternative residues for a given position within the recited peptide domain. In a further embodiment, X₃ and X₄ are independently selected from the group consisting of ELVEELK (SEQ ID NO: 90), ELLREIK (SEQ ID NO: 91), and ELVEEIE (SEQ ID NO: 92). In a still further embodiment, Z2 is selected from the group consisting of general formulae BX₁BX₂, X₁BBX₂, X₁BX₂B, and X₁X₂BB; and Z4 is selected from the group consisting of general formulae B₂X₃B₂X₄, X₃B₂B₂X₄, X₃B₂X₄B₂, and X₃X₄B₂B₂. In a further embodiment, the polypeptides of this aspect of the invention comprise a polypeptide that is at least 75% identical over its full length to the amino acid sequence selected from the group consisting of SEQ ID NOS:2-5.

In another embodiment of any aspect, embodiment, or combination of embodiments of the invention, the polypeptides are linked to a cargo. As used herein, the “cargo” can be any suitable component, including but not limited to nucleic acids, peptides, small molecules, amino acids, a detectable label, etc. In one non-limiting embodiment, the polypeptides of the invention can be modified to facilitate covalent linkage to a “cargo” of interest. In one non-limiting example, the polypeptides can be modified, such as by introduction of various cysteine residues at defined positions to facilitate linkage to one or more antigens of interest, such that a nanostructure of the polypeptides would provide a scaffold to provide a large number of antigens for delivery as a vaccine to generate an improved immune response. In some embodiments, some or all native cysteine residues that are present in the polypeptides but not intended to be used for conjugation may be mutated to other amino acids to facilitate conjugation at defined positions. In another non-limiting embodiment, the polypeptides of the invention may be modified by linkage (covalent or non-covalent) with a moiety to help facilitate “endosomal escape.” For applications that involve delivering molecules of interest to a target cell, such as targeted delivery, a critical step can be escape from the endosome—a membrane-bound organelle that is the entry point of the delivery vehicle into the cell. Endosomes mature into lysosomes, which degrade their contents. Thus, if the delivery vehicle does not somehow “escape” from the endosome before it becomes a lysosome, it will be degraded and will not perform its function. There are a variety of lipids or organic polymers that disrupt the endosome and allow escape into the cytosol. Thus, in this embodiment, the polypeptides can be modified, for example, by introducing cysteine residues that will allow chemical conjugation of such a lipid or organic polymer to the monomer or resulting assembly surface. In another non-limiting example, the polypeptides can be modified, for example, by introducing cysteine residues that will allow chemical conjugation of fluorophores or other imaging agents that allow visualization of the nanostructures of the invention in vitro or in vivo.

In another embodiment, the invention provides homo-oligomers (i.e.: homodimer, homotrimers, homotetramer, etc.) comprising a plurality of polypeptides of the present invention having the same amino acid sequence. As shown in the examples that follow, the polypeptides of the invention are capable of forming homo-oligomers with modular hydrogen bond network-mediated specificity.

In a further aspect, the present invention provides isolated nucleic acids encoding a polypeptide of the present invention. The isolated nucleic acid sequence may comprise RNA or DNA. As used herein, “isolated nucleic acids” are those that have been removed from their normal surrounding nucleic acid sequences in the genome or in cDNA sequences. Such isolated nucleic acid sequences may comprise additional sequences useful for promoting expression and/or purification of the encoded protein, including but not limited to polyA sequences, modified Kozak sequences, and sequences encoding epitope tags, export signals, and secretory signals, nuclear localization signals, and plasma membrane localization signals. It will be apparent to those of skill in the art, based on the teachings herein, what nucleic acid sequences will encode the polypeptides of the invention.

In another aspect, the present invention provides recombinant expression vectors comprising the isolated nucleic acid of any aspect of the invention operatively linked to a suitable control sequence. “Recombinant expression vector” includes vectors that operatively link a nucleic acid coding region or gene to any control sequences capable of effecting expression of the gene product. “Control sequences” operably linked to the nucleic acid sequences of the invention are nucleic acid sequences capable of effecting the expression of the nucleic acid molecules. The control sequences need not be contiguous with the nucleic acid sequences, so long as they function to direct the expression thereof. Thus, for example, intervening untranslated yet transcribed sequences can be present between a promoter sequence and the nucleic acid sequences and the promoter sequence can still be considered “operably linked” to the coding sequence. Other such control sequences include, but are not limited to, polyadenylation signals, termination signals, and ribosome binding sites. Such expression vectors can be of any type known in the art, including but not limited plasmid and viral-based expression vectors. The control sequence used to drive expression of the disclosed nucleic acid sequences in a mammalian system may be constitutive (driven by any of a variety of promoters, including but not limited to, CMV, SV40, RSV, actin, EF) or inducible (driven by any of a number of inducible promoters including, but not limited to, tetracycline, ecdysone, steroid-responsive). The construction of expression vectors for use in transfecting host cells is well known in the art, and thus can be accomplished via standard techniques. (See, for example, Sambrook, Fritsch, and Maniatis, in: Molecular Cloning, A Laboratory Manual, Cold Spring Harbor Laboratory Press, 1989; Gene Transfer and Expression Protocols, pp. 109-128, ed. E. J. Murray, The Humana Press Inc., Clifton, N.J.), and the Ambion 1998 Catalog (Ambion, Austin, Tex.). The expression vector must be replicable in the host organisms either as an episome or by integration into host chromosomal DNA. In various embodiments, the expression vector may comprise a plasmid, viral-based to vector, or any other suitable expression vector.

In a further aspect, the present invention provides host cells that comprise the recombinant expression vectors disclosed herein, wherein the host cells can be either prokaryotic or eukaryotic. The cells can be transiently or stably engineered to incorporate the expression vector of the invention, using standard techniques in the art, including but not limited to standard bacterial transformations, calcium phosphate co-precipitation, electroporation, or liposome mediated-, DEAE dextran mediated-, polycationic mediated-, or viral mediated transfection. (See, for example, Molecular Cloning: A Laboratory Manual (Sambrook, et al., 1989, Cold Spring Harbor Laboratory Press; Culture of Animal Cells: A Manual of Basic Technique, 2^(nd) Ed. (R. I. Freshney. 1987. Liss, Inc. New York, N.Y.). A method of producing a polypeptide according to the invention is an additional part of the invention. The method comprises the steps of (a) culturing a host according to this aspect of the invention under conditions conducive to the expression of the polypeptide, and (b) optionally, recovering the expressed polypeptide. The expressed polypeptide can be recovered from the cell free extract, but preferably they are recovered from the culture medium. Methods to recover polypeptide from cell free extracts or culture medium are well known to the person skilled in the art.

Examples

The modular and predictable nature of DNA interaction specificity is central to molecular biology manipulations and DNA nanotechnology, but without parallels in nature, it has not been evident how to achieve analogous programmable specificity with proteins. There are more polar amino acids than DNA bases, each of which can adopt numerous sidechain conformations in the context of different backbones, allowing for countless network possibilities. The inventors have developed a general computational method, HBNet™ was developed to rapidly enumerate all sidechain hydrogen bond networks possible in an input backbone structure (FIG. 1A).

Traditional protein design algorithms are not well suited for this purpose because the total system energy is generally expressed as the sum of interactions between pairs of residues for computational efficiency, and hence cannot clearly distinguish a connected hydrogen bond network from a set of disconnected hydrogen bonds. HBNet™ starts by precomputing the hydrogen bonding and steric repulsion interactions between all conformations (rotameric states) of all pairs of polar sidechains. These energies are stored in a graph data structure where the nodes are residue positions, positions close in three-dimensional space are connected by edges, and for each edge there is a matrix representing the interaction energies between the different rotameric states at the two positions. HBNet™ then traverses this graph to identify all networks of three or more residues connected by low energy hydrogen bonds with little steric repulsion (FIG. 1B). The most extensive and lowest energy networks (FIG. 1C) are kept fixed in subsequent design calculations at the remaining residue positions. Networks with buried donors and acceptors not making hydrogen bonds (unsatisfied) are rejected (FIG. 1D). Details of the method, as well as scripts for carrying out the design calculations, are described herein.

Inspired by the DNA double helix, it was attempted to host the hydrogen bond networks in protein oligomers with an inherent repeat structure to enable networks to be reutilized within the same scaffold. Attention was paid to coiled-coils, which are abundant in nature, the subject of many protein design studies, and can be generated parametrically, resulting in repeating geometric cross-sections. In natural and designed coiled coils, buried polar interactions can also alter specificity; however, most of these cases involve at most one or two sidechain-sidechain hydrogen bonds with remaining polar atoms satisfied by water or ions—the relatively small cross-sectional interface area of canonical coiled-coils limits the diversity and location of possible networks. To overcome these limitations, focus was placed on oligomeric structures with two concentric rings of helices (FIG. 1E).

“Two-ring” topologies were built from helical hairpin monomer subunits comprising an inner and outer helix connected by a short loop using a generalization of the Crick coiled-coil parameterization. Wide ranges of backbones were generated by systematically sampling the radii and helical phases of the inner and outer helices, the z-offset between inner and outer helices, and the overall supercoil twist (FIG. 1E). HBNet™ was then used to search these backbones for networks that span the intermolecular interface, have all heavy atom donors and acceptors satisfied, and involve at least three sidechains (FIG. 1F; because of these stringent requirements, only a small fraction of backbones can support such networks—but by systematically varying the degrees of freedoms of the two-ring structures, tens of thousands of backbones can be generated, and the efficiency of HBNet™ makes searching for networks in large numbers of backbones computationally tractable). RosettaDesign™ was then used to optimize rotamers at the remaining residue positions in the context of the cyclic symmetry of the oligomer (FIG. 1G). Designs were ranked based on the total oligomer energy using the Rosetta™ all atom force field, filtering to remove designs with large cavities or poor packing around the networks. The top-ranked designs were evaluated using Rosetta™ “fold-and-dock” calculations. Designs with energy landscapes shaped like funnels leading into the target designed structure were identified, and a total of 114 dimeric, trimeric, and tetrameric designs spanning a broad range of superhelical parameters and hydrogen bond networks were selected for experimental characterization.

Synthetic genes encoding the selected designs were obtained and the proteins expressed in Escherichia coli. The ˜90% (101/114) of designs that were expressed and soluble were purified by affinity chromatography, and their oligomerization state evaluated by size-exclusion chromatography multi-angle light scattering (SEC-MALS). Sixty-six of the 101 were found to have the designed oligomerization state. The 101 soluble designs span eight different topologies; of these, the supercoiled tetramers have the largest buried interface area, yielded the fewest designs with all buried donors and acceptors satisfied, and had the lowest success rate (only 3 of the 13 soluble designs properly assembled). Excluding supercoiled tetramers, 72˜(63/88) assembled to the designed oligomeric state, and of these, 89% (56/63) eluted as a single peak from the SEC column. The designed proteins were further characterized by circular dichroism (CD) spectroscopy; all designs tested exhibited characteristic a-helical spectra, and CD monitored unfolding experiments showed that more than 90% of these were stable at 95° C. (FIG. 2). Tested peptides include the following:

AXAX (SEQ ID NO: 2) TRTRSLREQEEIIRELERSLREQEELLRELERLQREGSSDEDVRE LLREIKKLAREQKYLVEELKKLAREQKRQD; XAAX (SEQ ID NO: 3) TRTEIIRELERSLREQERSLREQEELLRELERLQREGSSDEDVRE LLREIKKLAREQKKLAREQKYLVEELKRQD; XAXA (SEQ ID NO: 4) TRTEIIRELERSLREQEELAKRLKRSLREQERLQREGSSDEDVRK LAREQKELVEEIEKLAREQKYLVEELKRQD; and XXAA (SEQ ID NO: 5) TRTEIIRELEELAKRLKRSLREQERSLREQERLQREGSSDEDVRK LAREQKKLAREQKELVEEIEYLVEELKRQD

Polypeptide Nomenclature:

The name of the polypeptides shown below indicates oligomerization state and topology, and sequences below are organized by topology and oligomerization state. The first two characters indicate supercoil geometry: ‘2L’ refers to a two-layer heptad repeat that results in a left-handed supercoil; ‘3L’ refers to a three-layer 11-residue repeat with a right-handed supercoil; and ‘5.’ refers to untwisted designs with a five-layer 18-residue repeat and straight helices (no supercoiling), where “layer” in this context is the number of unique repeating geometric slices, or layers, along the supercoil axis. The middle two characters indicate the total number of helices, and the final two indicate symmetry. Thus, “2L6HC3” denotes a left-handed, six-helix trimer with C3 symmetry. Underlined residues are optional.

2L8HC4_12 (SEQ ID NO: 6) GTAIEANSRMLKALIEIAKAIWKALWANSLLLEATSRGDTERMRQ WAEEAREIYKEAKKIIDEADEIVKEAKERHD 5L6HC3_1 (SEQ ID NO: 7) SEELRAVADLQRLNIELARKLLEAVARLQELNIDLVRKTSELTDE KTIREEIRKVKEESKRIVEEAEEEIRRAKEESRYIADESRGS 2L4HC2_9 (SEQ ID NO: 8) GTSDYIIEQIQRDQEEARKKVEEAEERLERVKEASKRGVSSDQLL DLIRELAEIIEELIRIIRRSNEAIKELIKNQS 2L4HC2_11 (SEQ ID NO: 9) GSEDYKLREAQRELDKQRKDTEEIRKRLKEIQRLTDERTSTADEL IKELREIIRRLQEQSEKLREIIEELEKIIRKR 2L4HC2_23 (SEQ ID NO: 10) GTRTEIIRELERSLREQEELAKRLKELLRELERLQREGSSDEDVR ELLREIKELVEEIEKLAREQKYLVEELKRQD 2L4HC2_24 (SEQ ID NO: 11) GTDTDELLRLAKEQAELLKEIKKLVEEIARLVKEIQEDPSDELLK TLAELVRKLKELVEDMERSMKEQLYIIKKQKS 5L8HC4_6 (SEQ ID NO: 12) GSKDTEDSRKIWEDIRRLLEEARKNSEEIWKEITKNPDTSEIARL LSEQLLEIAEMLVRIAELLSRQTEQR 2L6HC3_AXAX (SEQ ID NO: 13) GTKYEIREALKEAQKQLEDLKRMLDELRRNLEELKRNPSEDALVE NNELIVRVLEVIVENNRSIIEILKLLAKSD 2L6HC3_AXBX (SEQ ID NO: 14) GTKYKIREMLEEAKRSLEELRRILEKLKESLRELRRNPSEDALVN NNEVIVKAIEASVENQRIIIELARMLAESD 2L6HC3_AXXB (SEQ ID NO: 15) GTKYRIKDTLRELKRALEELKKILEELQRSLEELRRNPSEDALVN NNEVIVKAIEAAVRAIEISAENQRMLAESD 2L6HC3_XAAA (SEQ ID NO: 16) GTKYEARKQLEEMKKQLKDLKRSLERLREILERLEENPSEDVIVE AIRAIVENNKQIVENNRSIIENNETIIRSD 2L6HC3_XBXA (SEQ ID NO: 17) GTKYELRRQLEELEKLLRELRKSLDELRKILEELERNPSEDVIVR AIKASVKNQEIIVEVLRAIIENNKTIAKSD 2L6HC3_12 (SEQ ID NO: 18) GTKYELRRALEELEKALQELREMLRKLKESLEELKKNPSEDALVR NNELIVEVLRVIVEVLSIIARVLEINARSD 2L6HC3_13 (SEQ ID NO: 19) GTKYELRRALEELEKALRELKKSLDELERSLEELEKNPSEDALVE NNRLNVENNKIIVEVLRIIAEVLKINAKSD 2L6HC3_6 (SEQ ID NO: 20) GTKYKIKETLKRLEDSLRELRRILEELKEMLERLEKNPDKDVIVE VLKVIVKAIEASVENQRISAENQKALAESD 2L6HC3_10 (SEQ ID NO: 21) GTKYEIKKALKELEEAIQKLKKSLKELKESLKELQKNPSEDALVK NNSLNVANNEIIVEVLEIIARILELLARSD 2L6HC3_11 (SEQ ID NO: 22) GTKYEIKEALRELNRALKELKEALRELERSLRELQKNPDKDALVR NNELNVDVARIIVEVLSIIARVLELLAKSD 2L6HC3_12 (SEQ ID NO: 23) GTKYELRRALEELEKALQELREMLRKLKESLEELKKNPSEDALVR NNELIVEVLRVIVEVLSIIARVLEINARSD 2L6HC3_13 (SEQ ID NO: 24) GTKYELRRALEELEKALRELKKSLDELERSLEELEKNPSEDALVE NNRLNVENNKIIVEVLRIIAEVLKINAKSD 2L6HC3_14 (SEQ ID NO: 25) GTKYELREAIRKLEEALRKLKKALDELRKSLEELKKNPSEDALVR NNELNVKVAEIIVKVLKIIAEAIKINAKSD 2L6HC3_19 (SEQ ID NO: 26) GTEEYKLRELLKRHNEVLKELQKAAKEAEEVAERFKKTNDITEAI RVIADLLRAIVKAIETNSRVVKMIVELNE 2L6HC3_2 (SEQ ID NO: 27) GTKYIEKLLREAQRTLEELKRLLEELKEMLKELERANATDARLIA EVIRVIVEVLRASVENQEMIIRILKAITEE 2L6HC3_23 (SEQ ID NO: 28) TEKDVLRIIVKNNEIIVKVLSVIAEVLKIIAKILENPSEYMLKEL KKALKELEKMLKELRKSLKELKEALRELEGS 2L6HC3_37 (SEQ ID NO: 29) GTLDYKLDEMLKKLEKSREEMEKMAQELRRALEELEKNSNVDKVL KIIIKAIQLSIENQKLNLEAVRLLIEAQKS 2L6HC3_6 (SEQ ID NO: 30) GTKYKIKETLKRLEDSLRELRRILEELKEMLERLEKNPDKDVIVE VLKVIVKAIEASVENQRISAENQKALAESD 2L8HC4_3 (SEQ ID NO: 31) GTDEYKWKEEVRRFEEEAKKWEEELKEMRKRIEDAKKGRPTLKVN LEAAEALLEAARLIVEAAKLLLAAAKLNEKQN 2L8HC4_9 (SEQ ID NO: 32) GSDEDRKAKELIERQRKLTDEAEEWAKQNEEIAKKIEKQPDTSLV ARMLANVSRMLLATNRALLANTEALEALIRKT 2L8HC4_12 (SEQ ID NO: 33) GTAIEANSRMLKALIEIAKAIWKALWANSLLLEATSRGDTERMRQ WAEEAREIYKEAKKIIDEADEIVKEAKERHD 3L6HC2_4 (SEQ ID NO: 34) SALEKIAKLIIEAARLSAELARRAARASAEMARKAIEAVSEERGS ESLLKIVADLIVESQEAVVRLIIESQQIAAKLAEDLIRAAKEAAS DESKMEEVAKEVQERAERAARDIERKLKRVLEELDYKLKESRDGS 3L6HC2_6 (SEQ ID NO: 35) TALEIAVRLNREAAREAARENADTARKAARRIAEVAKRLAEENRD AKLAARLLAEIARLLAELIARQSELLAEWLATQSKLAAELARKDT SATDEAERIRKESEELLDKVREEIKRLEDEVSKTIEELSERVRGS 3L6HC2_7 (SEQ ID NO: 36) SILELAHESNRRALEMASRANREAMKAAREMIRAASEAARRAGSS NDKDSLRMIEEALRLALRMIEETNKKAVRMVLENNRKMVEAEKKK LSEEEIKRIAKETEDRMREIARRASEEARRLAEEIKREADYRSGS 5L6HC3_1 (SEQ ID NO: 37) SEELRAVADLQRLNIELARKLLEAVARLQELNIDLVRKTSELTDE KTIREEIRKVKEESKRIVEEAEEEIRRAKEESRYIADESRGS 5L6HC3_3 (SEQ ID NO: 38) GTERKDRLRKELKRIAEETDKWVEELKEELERILRTIEELRKDPS SEVIVDIARIQLEALREVIRVVAENSKAILEAIHRVIEEG 5L6HC3_5 (SEQ ID NO: 39) SKEVRLQKLNAEIMKEIMELIIRLQEANARIIEELVRLIIDLERS TDSKRMIEEIRKVAERAIEESKRLLEEAEKAMRRAIYESEDALRE GS 5L8HC4_1 (SEQ ID NO: 40) GSKVEELLRKSEEAAERAKRELERLLEESERIVAEAQALAEKYES QKVWVRILIELIRATNRMLAEIARILLEMIEVTNRMIAESTK 5L8HC4_2 (SEQ ID NO: 41) SEQLKEIARILIKLIESLTRFILEVARILIELIEETQRLIVASTD SDESELERIARESKKKAKKALDELKKIVDDQRREAKKAIEELEYD GS 5L8HC4_6 (SEQ ID NO: 42) GSKDTEDSRKIWEDIRRLLEEARKNSEEIWKEITKNPDTSEIARL LSEQLLEIAEMLVRIAELLSRQTEQR 2L4HC2_1 (SEQ ID NO: 43) GTAYELLRKAEELEKKQQELLKRQEELAKTAEELRKKGGNADSMM KIIKESTRIVRESTEIVKELLKIIRELRRQS 2L4HC2_5 (SEQ ID NO: 44) GTRTEYLKKLAEEAKELAKRSRELSKESRRLSEEARRDPDKEKLL RVVKKLQEVIEELQRVIEELLRVIKEALENQS 2L4HC2_6 (SEQ ID NO: 45) GTETEYQRELAREARRLAKRSRELSERSRKLSEDAKRDPDKDKLL EVVERLQQVIEELQKVIEELLRVIESSLKTIS 2L4HC2_9 (SEQ ID NO: 46) GTSDYIIEQIQRDQEEARKKVEEAEERLERVKEASKRGVSSDQLL DLIRELAEIIEELIRIIRRSNEAIKELIKNQS 2L4HC2_10 (SEQ ID NO: 47) GTEEYRRKEQEERTKEQQERTERQRRKTEELKRATKEGTLTPEEA IRQAQKQSENAERQSREAEKQSREANEALRKR 2L4HC2_11 (SEQ ID NO: 48) GSEDYKLREAQRELDKQRKDTEEIRKRLKEIQRLTDERTSTADEL IKELREIIRRLQEQSEKLREIIEELEKIIRKR 2L4HC2_12 (SEQ ID NO: 49) GSEDYKLKELQKRNKKQEEEAKRNDDERKKIEELTRKRTSTADEL IRELQRSNEEMQRSQREMQDQSRRLEDIIRKR 2L4HC2_14 (SEQ ID NO: 50) GTEDYKRREAERKLQKQQEELKELKRKLEEIRELHEKGVGSPDRL IRELERIIRELQRMQKENEKIIKELQRIIKKR 2L4HC2_18 (SEQ ID NO: 51) GTESKYLLEEARRLKDEARKLKEEAKKVKEESRKLIERIDRGEDS DRELLERLKEQNNRLLEIIERLLEIIERLLKLIEEWTRDS 2L4HC2_19 (SEQ ID NO: 52) GTEEDYAEREIRKMKEEQKRQRKRLEELERELQEMQEKKREGTSD AKEVIDQLERIIRELQEIIRSQEDITRKLEEIIRRMKENS 2L4HC2_20 (SEQ ID NO: 53) GTNKEELKRTMEEQQRILEKLLRTIKEQKEILRKQEEGRATKEEL KRLTKLAQEQERMMRELIDLARKQAYLLKRES 2L4HC2_21 (SEQ ID NO: 54) GTREEKIRRILEEIQKIMEEIKRIMEEIKRTQEEAEKHGSSKKAI EKQKELLRRLEELLRKLERLLRELEYLMRDEK 2L4HC2_22 (SEQ ID NO: 55) GTREEWLYRILELIERIERLIKEIIRLSRRALELLENNASNEEWA QEIKEMQRKIQEWLKQILEWLKKIKEWIRESQ 2L4HC2_23 (SEQ ID NO: 56) GTRTEIIRELERSLREQEELAKRLKELLRELERLQREGSSDEDVR ELLREIKELVEEIEKLAREQKYLVEELKRQD 2L4HC2_24 (SEQ ID NO: 57) GTDTDELLRLAKEQAELLKEIKKLVEEIARLVKEIQEDPSDELLK TLAELVRKLKELVEDMERSMKEQLYIIKKQKS 5L4HC2_1 (SEQ ID NO: 58) GTEETKNSKRVLDIIEELMRQVEENSRELEKRIKELLRQTKEGKT KKELERDVRRTIEEQKKELRRLKEQVRKTKEEQREEQYRS 5L4HC2_2 (SEQ ID NO: 59) GTRTEKLMKEVEEIQRRQIELLKKLMKEVEDSSKRNQEATERGTT KKKWKEEQEKILEDLKREVRRIIEESRKWLEDLKKKVYES 5L4HC2_3 (SEQ ID NO: 60) GTEKYRLREEVRRTIEEQKENLERLKQEVKETERKTEEWRERNTT TEDAQREQIKIIRRLMKEVERNSRRLEKELRRLVEETRES 5L4HC2_6 (SEQ ID NO: 61) GTEKYRLIRESERALRELKRKVRELEEDQRERLDEQRKKVEEGQT TDELLRQNEENSRRMLKETKKLLREIERIQREQQRQNQEN 5L4HC2_7 (SEQ ID NO: 62) GTEKEKEIEKNSREVIKQVEDILRIKENSKRNIEIIKELQKDPSD EKMRETIEQQRENLERLERKARELIRRQERNLRETQYKD 5L4HC2_9 (SEQ ID NO: 63) GTEKYRIIEEQRRNLEDLEREIREIIKKLKEALERLRELVERNST NDRLLDEVRKIIEEAIEDMKRLLEKVERSIRQNIEELRRS 5L4HC2_10 (SEQ ID NO: 64) GTNKEYLRRKVKELKDQQKRNLEELEREVRRLIKEIEEWRERNTT TDRALKEIIRQIQRLLEEARRNSEEVLRQIEEIMEETRES 5L4HC2_11 (SEQ ID NO: 65) GTEEERALERIIRAIRELMREVERNSKEVLQWIKEMLRLTKENSS TKELEERWREIEERQRRNLEKLKEEVRRLEDEIRQETYRS 5L4HC2_12 (SEQ ID NO: 66) GTETKKLVEEVERALRELLKTSEDLVRKVEKALRELLELIRRGGT KDKIEEKIRRVLEEIKRELERQKRKIEDVLRQIKEELYRS 2L6Hanti_1 (SEQ ID NO: 67) SDYLRLATEHNKLAVEANRLAIELAKSAVELAETDPSKTALEHAE LAARLLEMMVQFTKAAQELTREAIRKEGRNEESEKVLRKSKEAYK ESEKALEDARRLLDELRKKGS 2L6Hanti_2 (SEQ ID NO: 68) SEELRKAAENNELAVRLAEAALRMARSALHLFEENPSDEMLKFLE LAMEVAKMAAELLKASLKMLKKAAEERGSDESVKYLADKSRDIMR QITEELKKLEEEAKRAQKRGS 2L6Hanti_3 (SEQ ID NO: 69) SEKARIAVENLEAALRLNRAAAEMQKSAIKIMDDNRSDEKALRYL RLTTKVLRMSVELLRASLELAEKALREEGSDDSAEKVRKEAEEIL KESTEILKEADKETKRADEEGS 2L6Hanti_4 (SEQ ID NO: 70) SRRLELAARINKAAAENARSAIEIQELAARLADELSSSKKVIDFA RATTEVLRMSVKLLKLSLEMLEEAARQDGRSEEVRYLAEESKKIL EEARKALEDADRLTKRIEEEGS 2L6Hanti_5 (SEQ ED NO: 71) TDVLRIAAENLKAAVELAKAALEMAKSAIEIAKTLTEDDEALKFA RAAAEVLRMAAKLLKLSIELARKAAEEEGSDDEVRYILDEARKQA DELREALKKVDEIMKELDKRGS 5H2LD_10 (SEQ ID NO: 72) TRRKQEMKRLKYEMEKIREETEEVKKEIEESKKRPQSESAKNLIL IMQLLINQIRLLALQIRMLALQLQE 5H2LD_13 (SEQ ID NO: 73) TEDQERLRKQMEYERKHTEKVEKEIRKVEQKMKSHEDTSLRLLVL IARLLINQIRLLILQIRSLSNLERN 5H2LD_15 (SEQ ID NO: 74) TESTLLILIMRLLVQQSELLQLQIQMLQLLLKANNGTNKTEIERR SKEMEEELKRMKESNREMTKRIKEME 5H2LD_18 (SEQ ID NO: 75) TESDLLRQISKLLIIQIRLLLLQIQMLILLLKMNTGTNTTQITKE AKRIEKEAQEARKELEKMQESNKKQT 6H2LD_8 (SEQ ID NO: 76) TEDEIRKLRKLLEEAEKKLYKLEDKTRRSEEISKTDDDPKAQSLQ LIAESLMLIAESLLIIAISLLLSSRNG 7H2LD_3 (SEQ ID NO: 77) TEDEELQRVEEEIRELERKAKELHYKSEEIRKKVNGRSPQAEALL MIAQALLNISESLLAIAKALLMIARST 8H2LD_4 (SEQ ID NO: 78) TDEREIIKRVKRLLEEVEYLIERLRDQIEKAEKGLLDSRKAQQNA EALVNLIKAMVLVLKALLLAKELER 8H2LD_4_KE (SEQ ID NO: 79) TEEQYIIEEVKKLLEEVKKLIEELKKQIEKAEKGEEDSRKAQQNA EALVNLIKAMVLVLKALLLAKELER

To probe the energetic contribution of the outer ring of helices, the stability of the two-ring designs was compared to corresponding designs with only the inner ring; core interface positions of the inner helices, including hydrogen bond network residues, were retained and solvent-exposed surface positions were redesigned in the same manner as the surface of the two-ring designs. 2L4HC2_9 (FIG. 2C), a supercoiled homodimer is folded and thermostable (FIG. 2D); its inner helix peptide, 2L4HC2_9 inner (FIG. 2E), also forms a homodimeric coiled-coil, but with markedly decreased thermostability (FIG. 2F). 2L6HC3_13 (FIG. 2G), a supercoiled homotrimer is also folded and thermostable (FIG. 2H); however, the corresponding inner ring peptide (FIG. 2I) in isolation is unfolded (FIG. 2J) and monomeric. The sequence of this inner helix is notable because it has four Asn residues at canonical a or d heptad packing positions where Asn is destabilizing, and also because its other a and d positions are Leu and Ile respectively, which has been found to favor homotetramers. In the presence of the outer helix and designed hydrogen bond networks, the two-ring design assembles to the intended trimeric structure as elucidated by x-ray crystallography (FIG. 3A). Together, these results suggest that the outer ring of helices not only increases thermostability but also can drive coiled-coil assembly, even in the context of an inner helix with low helical propensity and non-canonical helical packing, permitting greater sequence diversity across larger interfaces.

Structural Characterization

To assess the accuracy of the designs, ten crystal structures were determined spanning a range of oligomerization states, superhelical parameters, and hydrogen bond networks (FIG. 3A-F). Designs for which crystals were not obtained were characterized by small angle x-ray scattering (SAXS) (FIG. 4). Structures for three left-handed trimers, four left-handed dimers, a left-handed tetramer, and an untwisted triangle-shaped trimer were solved. Additional topologies characterized by SAXS include square-shaped untwisted tetramers (FIG. 4A) and dimers (FIG. 4B), as well as six-helix dimers (two inner, one outer helix) with either parallel right-handed (FIG. 4C) or antiparallel left-handed (FIG. 4D) supercoil geometry. Five of the x-ray crystallography-verified designs (FIG. 3A,C-F) were also characterized by SAXS, and the experimentally determined spectra were found to closely match those computed from the design models, suggesting that very similar structures are populated in solution.

The three left-handed trimer structures (2L6HC3_6, 2L6HC3_12, and 2L6HC3_13) are remarkably similar to the design models with sub-angstrom RMSD across all backbone Cα atoms and across all heavy atoms of the hydrogen bond networks (FIG. 3A-B). These structures are constructed with supercoil phases of 0, 120 and 240 degrees for the inner helices, and 60, 180, and 300 degrees for the outer helices; loops connect outer N-terminal helices to inner C-terminal helices (at −60 degrees from the outer helix). Extensive nine or twelve-residue networks form the intended hydrogen bonds in the crystal structures (FIGS. 3, A and B middle). Unlike previously designed single-ring trimers where three buried asparagines resulted in substantially decreased thermostability, these two-ring trimers are stable up to 95° C. and ˜4.5M guanidinium chloride with numerous buried polar residues; 2L6HC3_13 has twelve completely buried asparagines, and 2L6HC3_6 has 24 buried polar residues confined to a small region of the interface, including six asparagines and six glutamines.

The four left-handed dimer crystal structures (2L4HC2_9, 2L4HC2_23, 2L4HC2_11, and 2L4HC2_24) all have the designed parallel two-ring topology. Two of the dimer structures have hydrogen bond networks in close agreement to the designs: 2L4HC2_9 (FIG. 3D) and 2L4HC2_23 (FIG. 3E) have 0.39 Å and 0.92 Å RMSD across all network residue heavy-atoms, respectively, and 0.39 Å and 1.16 Å RMSD over all Cα atoms. The other two, 2L4HC2_11 and 2L4HC2_24, have slight structural deviations from the design models caused by water displacing designed network sidechains; in the former, the interface shifts ˜2 Å due to a buried water molecule bridging two network residues, and in the latter, the backbone is nearly identical to the design model but sidechains of the designed network are displaced by ordered water molecules. These two cases highlight the need for high connectivity and satisfaction (all polar atoms participating in hydrogen bonds) of the networks. The lefthanded tetramer structure has the designed overall topology (FIG. 3C), and SAXS data is in close agreement with the design model, but sidechain density was uncertain due to low (3.8 Å) resolution. The amino acid sequence is unrelated to any known sequence, and the top hit in structure-based searches of the Protein Data Bank (PDB) has a quite different helical bundle arrangement.

The five antiparallel six-helix dimers (2L6Hanti_1-5) were soluble and assembled to the designed oligomeric state, with SAXS data in agreement with the design models (FIG. 4D). Design 2L6Hanti_3 contains a hydrogen bond network with a buried Tyr at the dimer interface (FIG. 4D). Of the three right-handed six-helix dimers characterized by SAXS, 3L6HC2 4 (FIG. 4C) and 3L6HC2 7 exhibited scattering in agreement with the design models, whereas 3L6HC2 2 did not. While 3L6HC2 2 was designed to form a parallel dimer, its crystal structure revealed an antiparallel dimer interface, highlighting two design lessons: first, the importance of intermolecular hydrogen bonds at the binding interface (the 3L6HC2 2 design model has only two across the interface compared to 9 in 2L6HC3_6 (FIG. 3B)), and second, the importance of favorable hydrophobic contacts complementing the networks (the 3L6HC2 2 design model has mainly alanines at the interface).

SAXS data suggest that untwisted dimer, trimer and tetramer designs assemble into the target triangular and square conformations (FIG. 4A-B). Guinier analysis and fit of the low-q region of the scattering vector indicates that the seven untwisted dimers tested are in the correct oligomeric state, four of which have very close agreement between the experimental spectra and design models (FIG. 4B). The SAXS data on the three untwisted tetramers (5L8HC4_1, 5L8HC4_2, and 5L8HC4_6) were all in close agreement with the corresponding design models (FIG. 4A). 5L8HC4_6 has a distinctive network with a Trp making a buried hydrogen bond at one end of the network, which then propagates outwards towards solvent, connecting to an Glu on the surface (FIG. 4A). It is believed that oligomers with such uniformly straight helices do not exist in nature, nor have these topologies been designed previously.

The 2.36 Å crystal structure of the untwisted trimer (5L6HC3_1) reveals straight helices with 0.51 Å RMSD to the design model over all Cα atoms (FIG. 3F). The two hydrogen bond networks (FIG. 3F middle), as well as the hydrophobic packing residues surrounding the networks (FIG. 3F right), are nearly identical between the crystal structure and design model, with 0.41 Å and 0.48 Å RMSD over all network heavy-atoms. Like the supercoiled trimers, each of these networks contains sidechains from every helix, and helices were constructed to be uniformly symmetrical and equidistant. The helices are nearly perfectly straight in the crystal structure with supercoil twist values very close to the idealized design value of zero: ω₀=−0.036 degrees/residue for the inner three helices and to ω₀=−0.137 degrees/residues for the outer three helices. Blast searches with the amino acid sequence returned no matches with E-values better than 10, and the top hit in a search for similar structures in the PDB has three supercoiled helices flanked by long extended regions.

Comparison of Successful Versus Unsuccessful Network Designs

Several trends emerged distinguishing successful designs. First, in successful designs nearly all buried polar groups made hydrogen bonds. Designs with all heavy atom donors and acceptors satisfied were selected, but the networks had varying numbers of polar hydrogens unsatisfied. Networks with the largest fraction of satisfied polar groups generally had relatively high connectivity, both with respect to the total number of hydrogen bonds and number of sidechains contributing to the network. Networks with the highest connectivity and structural accuracy were those that spanned the entire cross-sectional interface, with each helix contributing at least one sidechain (FIG. 3A, 3B, 3E, 3F). Design 2L6HC3_13 also has two additional smaller networks comprising a single symmetric Asn making two hydrogen bonds but with one polar hydrogen unsatisfied; in the crystal structure, these residues move away from the design model, displaced by water molecules.

The Designed Hydrogen Bond Networks Confer Specificity

To test the role of the designed hydrogen bond networks in conferring specificity for the target oligomeric state, control design calculations were carried out using the same protein backbones without HBNet™, yielding uniformly hydrophobic interfaces. In silico, despite having lower total energy in the designed oligomeric state, these designs exhibit more pronounced alternative energy-minima in fold-and-dock and asymmetric docking calculations, consistent with the much less restrictive geometry of nonpolar packing interactions. Experimentally, these hydrophobic designs exhibited less soluble expression than their counterparts with hydrogen bond networks and tended to precipitate during purification; of those that remained in solution long enough to collect SEC-MALS data, all but one formed higher molecular weight aggregates, eluting as multiple peaks from the SEC column. These results suggest that the designed hydrogen bond networks confer specificity for the target oligomeric state and resolve the degeneracy of alternative states observed with purely hydrophobic packing (this degeneracy is considerably more pronounced for herein-described 2 ring structures than traditional single ring coiled coils, which have many fewer total hydrophobic residues and less inter-helical interface area).

An in vivo yeast-two-hybrid assay was used to further probe the interaction specificity of the designed oligomers. Sequences encoding a range of dimers, trimers, and tetramers were crossed against each other in all-by-all binding assays (FIG. 5); synthetic genes for the designs were cloned in frame with both DNA-binding domains and transcriptional activation domains in separate vectors such that binding of the designed protein interaction is necessary for cell growth. Designs in which the hydrogen bond networks partition hydrophobic interface area into relatively small regions are considerably more specific than designs with large contiguous hydrophobic patches at the helical interface (FIGS. 5, A and B). The designs with the best-partitioned hydrophobic area had networks spanning the entire oligomeric interface, with each helix contributing at least one sidechain. This unifying design principle can readily be enforced using HBNet™.

To test if regular arrays of networks can confer specificity in a modular, programmable manner, an additional set of trimers were designed, each with identical backbones and hydrophobic packing motifs, the only difference being placement and composition of the hydrogen bond networks. The designs are based on 2L6HC3_13 (FIG. 3A) and 2L6HC3_6 (FIG. 3B), which originated from the same superhelical parameters but have unique networks referred to as “A” and “B”, respectively; cross-sections with only nonpolar residues are labeled “X”. This three-letter code was used to generate new designs in combinatorial fashion: at each of the 4 repeating cross-sections of the supercoil (FIG. 5C), either the A, B, or X (FIG. 4D) were placed followed by the same design strategy and selection process as before. Six of these combinatorial designs were synthesized and 5/6 were found to be folded, thermostable, and assembled to the designed trimeric oligomerization state in vitro. These five, along with the two parent designs (2L6HC3_13=AAXX and 2L6HC3_6=XXBB) and an all-hydrophobic control (XXXX), were crossed in all-by-all yeast-two-hybrid binding experiments (FIG. 5E). The combinatorial designs exhibit a level of specificity that is striking given that all have identical backbones and high overall sequence similarity, whereas the hydrophobic control is relatively promiscuous; the central hydrogen bond networks are clearly responsible for mediating specificity.

Previous de novo protein design efforts have focused on jigsaw-puzzle-like hydrophobic core packing to design new structures and interactions. Unlike the multi-body problem of designing highly connected and satisfied hydrogen bond networks, hydrophobic packing is readily captured by established pairwise-decomposable potentials; consequently, most protein interface designs have been predominantly hydrophobic, and attempts to design buried hydrogen bonds across interfaces have routinely failed. Polar interfaces have been designed in specialized cases but have been difficult to generalize, with many interface design efforts requiring directed evolution to optimize polar contacts and achieve desired specificity. HBNet™ now provides a general computational method to accurately design hydrogen bond networks. This ability to precisely pre-organize polar contacts without buried unsatisfied polar atoms should be broadly useful in protein design challenges such as enzyme design, small molecule binding, and polar protein interface targeting.

Two-ring structures are a new class of protein oligomers that have the potential for programmable interaction specificity analogous to that of Watson-Crick base paring. Whereas Watson-Crick base pairing is largely limited to the antiparallel double helix, the designed protein hydrogen bond networks allow the specification of two-ring structures with a range of oligomerization states (dimers, trimers, and tetramers) and supercoil geometries. Adding an outer ring of helices to enable hydrogen bond networks extends upon elegant studies from Keating, Woolfson, and others demonstrating the designability of coiled coils with a wide range of hetero and homo-oligomeric specificities. The design models and crystal structures show that a wide range of hydrogen bond network composition and geometry are possible in repeating two-ring topologies, and that multiple networks can be engineered into the same backbone at varying positions without sacrificing thermostability, enabling stable building blocks with uniform shape but orthogonal binding interfaces (FIG. 5). The DNA nanotechnology field has demonstrated that a spectacular array of shapes and interactions can be built from a relatively limited set of hydrogen bonding interactions. It should now become possible to develop new protein-based materials with the advantages of both polymers: DNA-like programmability and tunable specificity, coupled with the geometric variability, interaction diversity, and catalytic function intrinsic to proteins.

Computational Techniques

Computational techniques related to protein design based on a Hydrogen Bond Network method (HBNet™) are described in detail below. The HBNet™ method can include three steps. First, an exhaustive but efficient search identifies the hydrogen bond networks possible within a given search space (which consists of all allowed sidechain rotamers of all amino acid types being considered for a particular backbone conformation). Second, networks are scored and ranked based on the Rosetta™ energy function, satisfaction (all buried polar atoms participating in hydrogen bonds), and user-defined options. And, third, the best networks, or combinations of the best networks, are iteratively placed onto the design scaffold and held in relative position with constraints that serve as ‘seeds’ for any subsequent Rosetta™ method to design around the network and optimize rotamers for the remaining positions in the scaffold.

Step 1. Exhaustive Search to Identify all Possible Hydrogen Bond Networks in the Given Search Space (FIG. 1A-B).

HBNet™ makes use of Rosetta™'s Interaction Graph (IG) data structure, initially populating it with only the sidechain hydrogen bond and Lennard-Jones (steric repulsive) energy terms. The nodes of the graph are the residue positions of all designable or packable residues, and the edges represent putative interactions between those residues, pointing to sparse matrices that store the two-body energies between all pairs of interacting rotamers (of all amino acid types being considered) at those two positions. Only using the hydrogen bond and repulsive energies allows for instant look-up of all rotamer pairs with favorable (low energy) hydrogen bond geometry and no steric clashing. In some embodiments, Monte Carlo or similar randomized methods can be used to search this rotamer interaction space.

In other embodiments, the entire rotamer interaction space can be searched. The search through the entire rotamer interaction space can be performed using a recursive depth-first search or a recursive breadth-first search of the interaction graph, enumerating all compatible, non-clashing connectivitics of hydrogen bonded sidechain rotamers. Since the search traverses not only the nodes of the graph, but also matrices pointed to by each edge (multiple rotamers per each node, and multiple pairs of rotamers for each edge), implementation of a graph traversal algorithm for this graph can consider connected nodes (residues positions) of networks as well as considering hydrogen bonds between atoms of particular rotamers at each node—this latter hydrogen-bond criteria requires additional steps and behavior for this graph traversal algorithm.

Each time a new hydrogen bonding rotamer is considered, the graph traversal algorithm can check the rotamer to ensure it does not clash with any existing rotamers in that network. If it is accepted, a recursive call is made on this rotamer. These recursive calls continue until a stop condition is reached: either no additional hydrogen bonding interactions can be found, or the network connects back to one of the original starting residues.

Some polar amino acids, such as Asn and Gln, can make three or more hydrogen bonds, serving as branch points in hydrogen bond networks; depth-first search misses these branching amino acids, and to account for this, a look-back function identifies networks that share one or more identical rotamers and, after checking for clashes or conflicting residues, merges them together into complete networks. Redundant networks are eliminated.

An instance of HBNet™, “HBNetStapleInterface™”, was written, in which graph traversals are initiated at residue positions at the intermolecular interface. This implementation of HBNet™ offers two advantages: first, starting the traversal at only the interface positions reduces the search space, speeding up runtime, and second, it ensures only networks at the interface are found, which was the goal of the approach in this study; requiring that at least 2 residues in each network come from different polypeptide chains ensure that network spans the intermolecular interface. For each starting residue, HBNetStapleInterface™ iterates through each edge; at each edge, networks are initiated for rotamer pairs with interaction energies less than a threshold value (default=−0.75). Because the interaction energy only consists of hydrogen bonding and repulsive contributions, a positive energy indicates clashing, and a negative energy indicates hydrogen bonding; setting a threshold allows for both selection of hydrogen bonds with favorable (low energy) geometry and faster computational runtime—because of the multiple recursive steps, runtime is exponential dependent upon the number of hydrogen bonding rotamer pairs (which increases as the threshold is made less stringent). The total number of hydrogen bonding rotamer pairs differs vastly between input structures and cannot be calculated ahead of time; through extensive empirical testing, threshold values were found ranging from −0.65 to 0.85 resulted in favorable hydrogen bonds and runtimes on the order of ˜0.2-10 minutes for complete design runs that included downstream design of numerous network possibilities for a given input structure.

Step 2. Score and Rank all of the H-Bond Networks.

Once all possible networks are identified, the identified networks are scored and ranked to determine the “best” networks. For each network, buried polar atoms are identified by solvent-accessible surface area (SASA); networks with buried heavy atom donors or acceptors not making hydrogen bonds (unsatisfied) are eliminated. The remaining networks are then ranked based on the least number of unsatisfied polar hydrogens. The networks are then scored against each other in the context of a background reference structure: all designable or packable positions in the scaffold are mutated to poly-alanine, network rotamers placed onto the scaffold, and the network scored with the full Rosetta™ energy function (talaris2013).

During Step 1, sidechain-backbone hydrogen bonds are not explicitly considered because the backbone is fixed (the number of sidechain-backbone hydrogen bonds for any given rotamer is constant). During Step 2, sidechain-backbone hydrogen bonds are scored when the networks are placed onto the reference structure, and are therefore included in evaluation for satisfaction (how many of the buried polar atoms participate in hydrogen bonds). Thus, even though they are not searched for explicitly, HBNet™ captures networks with sidechain-backbone hydrogen bonds. Networks with additional hydrogen bonds to backbone polar atoms will generally score better than a similar network without h-bonds to backbone in that the connectivity and satisfaction is improved.

Step 3. For Each of the Best-Scoring H-Bond Networks, Perform Design.

The best networks as ranked by Step 2 are iteratively placed onto the input scaffold and passed back to the RosettaScripts™ protocol and for user-defined design of the remaining residue positions. Atom-pair constraints are automatically turned on for each pair of atoms making a hydrogen bonds in the network; these constraints are tracked throughout the remainder of the design run to ensure the network residues are fixed in relative position during the downstream design. HBNet™ also outputs a Rosetta™ constraint (.cst) file that can be used to specify the same constraints in subsequent Rosetta design runs.

It should be noted that these atom-pair “constraints” in Rosetta™ nomenclature are really “restraints” in that the rotamers are allowed to move, and an energy penalty is applied if the constraint is broken (i.e., if the hydrogen bond is broken). This approach—as opposed to simply fixing the coordinates of the network atoms—allows small movements of the network rotamers, allowing for a larger number of solutions for packing additional rotamers around the network. A trend that emerged that tight packing around the networks, as well as satisfaction of all buried heavy-atom donors and acceptors, is paramount to design success; it is more important to have hydrogen bonds satisfying all polar atoms in the network with mediocre h-bond geometry than it is to have ideal h-bond geometry but poor packing around them and/or unsatisfied donors/acceptors.

Combinations of multiple networks at the same interface can also be considered and specified by the user. Unlike typical Rosetta™ design, in which one input structure yields one output structure (the lowest energy solution found by sequence design and combinatorial sidechain optimization), this approach allows for hundreds of design possibilities to be output for each input structure.

Defining the Search Space (which Amino Acid Types and Sidechain Rotamers are Allowed During Network Search)

HBNet™ will only search for networks within a given search space (all possible rotamers of all possible amino acid types being considered for a given input backbone), which can be defined by the user. HBNet™ functions as a “Mover” within the RosettaScripts™ framework and can be passed “task operations” to specify which residue positions are fixed, packable (amino acid type is fixed but sidechain conformation is not), and designable—for designable positions, task operations can also specify which amino acid types are allowed at each position. The default setting in the absence of any task operations is that all residues are considered for design and all polar amino acids are considered in the network search.

All positions in the scaffold can be set to be designable; for HBNet™, buried positions (defined based on solvent-accessible surface area (SASA)) can be allowed to be any noncharged polar amino acid, and solvent-exposed positions can be allowed to be any polar amino acid.

Computational Design

A generalization of the Crick coiled-coil parameters was used to independently vary parameters of two or more helices supercoiled around the same axis, parameters defined as described previously. Each monomer subunit has at least one inner helix and an outer helix (FIG. 1D). The supercoil phase (Δφ_(0 in)) and z-offset of the first inner helix were fixed to 0 to serve as a relative reference point; all other parameters varied independently between the inner and outer helices, with the exception of the supercoil twist (ω₀) and helical twist (ω₁). Because these two parameters are coupled and determine handedness, ideal values were used for ω₁ with ω₀ and ω₁ held constant between the inner and outer helices for the majority of designs. A left-handed supercoil results from ω0<0 and ω1=102.85, a right-handed supercoil from ω₀>0 and ω₁=98.18, and a straight bundle (no supercoiling) from ω0=0 and ω1=100. For the parallel six-helix dimer designs (3L6HC2), which have two inner helices and one out helix, ω0 of the outer helix was allowed deviate from that of the inner helix, but was required to be positive to maintain a right-handed supercoil.

Additional sets of supercoiled dimer backbones were generated by constraining the pitch of the outer helix to match that of the inner helix via the following equation:

$\omega_{0}^{\prime} = \frac{\omega_{0}}{\sqrt{\frac{1 + {\omega_{0}^{2}\left( {R^{\prime\; 2} - R^{2}} \right)}}{d^{2}}}}$

where:

-   -   ω₀′: superhelical twist of outer helix     -   ω₀: superhelical twist of inner helix     -   R′: superhelical radius of outer helix     -   R: superhelical radius of outer helix     -   d: rise per residue (set to 1.51)

Constraining the pitch results in the outer helix maintaining more contacts to the inner helices throughout the length of the helical bundle allows for different hydrogen bond network and packing solutions.

HBNet™ is written in C++ as part of the Rosetta™ software suite: HBNet™ was developed to be modular and is compatible with all symmetric Rosetta™ applications, as well as the RosettaScripts™ XML framework so that it can be plugged into most existing design protocols, and users can customize options specific to their design tasks. HBNet™ is written as an abstract base class, from which specialized “mover” classes can be derived for specific design cases. In particular, the instance of HBNet™ described herein as “HBNetStapleInterface™” was written to search for hydrogen bond networks that span across intermolecular interfaces. AB

Table 1 shows example RosettaScripts™ XML used for design calculations, example command lines and flags used for design calculations, and customized score weighting information.

TABLE 1 <ROSETTASCRIPTS>#Design of symmetric homo-oligomers using HBNet, updated to work with new XSD <SCOREFXNS> <ScoreFunction name=“hard_symm” weights=“talaris2013_cst” symmetric=“1”> <Reweight scoretype=“coordinate_constraint” weight=“0.5” /> </ScoreFunction> <ScoreFunction name=“hard_bb” weights=“bb_only” symmetric=“1”> <Reweight scoretype=“coordinate_constraint” weight=“2.” /> <Reweight scoretype=“cart_bonded” weight=“0.5” /> </ScoreFunction> <ScoreFunction name=“hard_symm_no_cst” weights=“talaris2013” symmetric=“1”/> </SCOREFXNS> <TASKOPERATIONS> <InitializeFromCommandline name=“init”/> <IncludeCurrent name=“current”/> <LimitAromaChi2 name=“arochi” /> <ExtraRotamersGeneric name=“ex1_ex2” ex1=“1” ex2=“1”/> <ExtraRotamersGeneric name=“ex1” ex1=“1”/> <RestrictAbsentCanonicalAAS name=“ala_only” resnum=“0” keep_aas=“A” /> <LayerDesign name=“init_layers” layer=“other” make_pymol_script=“0”> <TaskLayer> <SelectBySASA name=“symmetric_inteface_core” state=“bound” mode=“mc” core=“1” probe_radius=“2.0” core_asa=“35” surface_asa=“45” verbose=“1”/> <all copy_layer=“core” /> <Helix append=“NQSTH”/> </TaskLayer> <TaskLayer> <SelectBySASA name=“symmetric_inteface_surface” state=“bound” mode=“mc” surface=“1”probe_radius=“2.0” core_asa=“35” surface_asa=“45” verbose=“1”/> <al1 copy_layer=“surface” /> </TaskLayer> <TaskLayer> <SelectBySASA name=“symmetric_intefacc_boundary” state=“bound” mode=“mc” boundary=“1” probe_radius=“2.0” core_asa=“35” surface_asa=“45” verbose=“1”/> <all copy_layer=“boundary” /> <Helix exclude=“EKRW”/> </TaskLayer> </LayerDesign> <SelectBySASA name=“select_core” state=“bound” mode=“mc” core=“1” probe_radius=“2.0” core_asa=“35” surface_asa=“45” verbose=“1”/> <SelectBySASA name=“select_boundary” state=“bound” mode=“mc” boundary=“1” probe_radius=“2.0” core_asa=“35” surface_asa=“45” verbose=“1”/> <SelectBySASA name=“select_surface” state=“bound” mode=“mc” surface=“1” probe_radius=“2.0” core_asa=“35” surface_asa=“45” verbose=“1”/> <SelectBySASA name=“select_all” state=“bound” mode=“mc” core=“1” boundary=“1” surface=“1” probe_radius=“2.2” core_asa=“35” surface_asa=“45” verbose=“1”/> </TASKOPERATIONS> <FILTERS> <EnzScore name=“cst_score” score_type=“cstE” scorefxn=“hard_symm” whole_pose=“1” energy_cutoff=“10.0”/> <SymUnsatHbonds name=“uhb” cutoff=“1000”/> <Holes name=“holes” threshold=“1.8” confidence=“0”/> <PackStat name=“packstat” threshold=“0.65” confidence=“0”/> <PackStat name=“init_pstat” threshold=“0.575” confidence=“0”/> <ScoreType name=“cart_bonded_filter” scorefxn=“hard_symm” score_type=“cart_bonded” threshold=“30.” confidence=“1.” /> <Geometry name=“geo” omega=“165” cart_bonded=“35” confidence=“1”/> </FILTERS> <MOVERS> #define symmetry of homo-oligomer; in this example, it's C3 symmetry <SetupForSymmetry name=“setup_symm” definition=“C3_Z.sym”/> <SymPackRotamersMover name=“transform_sc” scorefxn=“hard_symm” task_operations=“ala_only” /> <AddConstraintsToCurrentConformationMover name=“add_cst” use_distance_cst=“0”max_distance=“12.” coord_dev=“2.5” min_seq_sep=“8” /> <ClearConstraintsMover name=“clearconstraints”/> <SymMinMover name=“hardmin_bb” scorefxn=“hard_bb” type=“lbfgs_armijo_nonmonotone” tolerance=“0.0001” chi=“1” bb=“1” bondangle=“1” bondlength=“1” jump=“all” cartesian=“1”/> #HBNet Mover definition <HBNetStapleInterface name=“hbnet_interf” hb_threshold=“−0.75” upper_score_limit=“3.5” write_network_pdbs=“1” pore_radius=“3.5” minimize=“0” min_helices_contacted_by_network=“6” min_network_size=“6” max_unsat=“2” max_staples_per_interface=“4” combos=“2” stringent_satisfaction=“1” onebody_hb_threshold=“−0.3” task_operations=“init,current,arochi,ex1_ex2,init_layers” /> #MultiplePoseMover (MPM) is needed because HBNet will pass back multiple poses -- one for each network, or combination of networks that is tried # The MPM collects all poses passed to it by HBNet, and then runs a nested ROSETTASCRIPTS protocol iteratively on each pose # Constraints are automatically turned on to keep the given network fixed in relative position during downstream design <MultiplePoseMover name=“MPM_design” max_input_poses=“100”>  <SELECT>  </SELECT>  <ROSETTASCRIPTS> <SCOREFXNS> <ScoreFunction name=“soft_symm” weights=“soft_rep_trp_ala” symmetric=“1”/> <ScoreFunction name=“hard_symm” weights=“talaris2013_cst” symmetric=“1”> <Reweight scoretype=“coordinate_constraint” weight=“0.5” /> </ScoreFunction> <ScoreFunction name=“up_ele” weights=“talaris2013” symmetric=“1”> <Reweight scoretype=“fa_elec” weight=“1.4” /> <Reweight scoretype=“hbond_sc” weight=“2.0” /> </ScoreFunction> </SCOREFXNS> <TASKOPERATIONS> <InitializeFromCommandline name=“init”/> <IncludeCurrent name=“current”/> <LimitAromaChi2 name=“arochi” /> <ExtraRotamersGeneric name=“ex1_ex2” ex1=“1” cx2=“1”/> <ExtraRotamersGeneric name=“ex1” ex1=“1”/> <LayerDesign name=“all_layers” layer=“other” make_pymol_script=“0”> <TaskLayer> <SelectBySASA name=“symmetric_inteface_core” state=“bound” mode=“mc” core=“1” probe_radius=“2.0” core_asa=“35” surface_asa=“45” verbose=“1”/> <all copy_layer=“core”/> <Helix append=“M”/> </TaskLayer> <TaskLayer> <SelectBySASA name=“symmetric_inteface_surface” state=“bound” mode=“mc” surface=“1” probe_radius=“2.0” core_asa=“35” surface_asa=“45” verbose=“1”/> <all copy_layer=“surface” /> </TaskLayer> <TaskLayer> <TaskLayer> <SelectBySASA name=“symmetric_inteface_boundary” state=“bound” mode=“mc” boundary=“1” probe_radius=“2.0” core_asa=“35” surface_asa=“45” verbose=“1”/> <all copy_layer=“boundary” /> <Helix exclude=“D”/> </TaskLayer> </LayerDesign> <SelectBySASA name=“select_core” state=“bound” mode=“mc” core=“1” probe_radius=“2.0” core_asa=“35” surface_asa=“45” verbose=“1”/> <SelectBySASA name=“select_boundary” state=“bound” mode=“mc” boundary=“1” probe_radius=“2.0” core_asa=“35” surface_asa=“45” verbose=“1”/> <SelectBySASA name=“select_surface” state=“bound” mode=“mc” surface=“1” probe_radius=“2.0” core_asa=“35” surface_asa=“45'' verbose=“1”/> <ConstrainHBondNetwork name=“hbnet_task” /> </TASKOPERATIONS> <MOVERS> <SymPackRotamersMover name=“softpack_core” scorefxn=“soft_symm” task_operations=“init,all_layers,select_core,current,arochi,hbnet_task”/> <SymPackRotamersMover name=“softpack_boundary” scorefxn=“soft_symm” task_operations=“init,all_layers,select_boundary,current,arochi,hbnet_task”/> <SymPackRotamersMover name=“softpack_surface” scorefxn=“soft_symm” task_operations=“init,all_layers,select_surface,current,arochi,hbnet_task”/> <SymPackRotamersMover name=“hardpack_core” scorefxn=“hard_symm” task_operations=“init,all_layers,select_core,current,arochi,ex1_ex2,hbnet_task”/> <SymPackRotamersMover name=“hardpack_boundary” scorefxn=“hard_symm” task_operations=“init,all_layers,select_boundary,current,arochi,ex1_ex2,hbnet_task”/> <SymPackRotamersMover name=“hardpack_surface” scorefxn=“up_ele” task operations=“init,all_layers,select_surface,current,arochi,ex1,hbnet_task”/> <SymMinMover name=“hardmin_sconly” scorefxn=“hard_symm” chi=“1” bb=“0” bondangle=“0” bondlength=“0” /> </MOVERS> <APPLY_TO_POSE> </APPLY_TO_POSE> <PROTOCOLS> <Add mover=“softpack_core”/> <Add mover=“softpack_boundary”/> <Add mover=“softpack_surface”/> <Add mover=“hardmin_sconly”/> <Add mover=“hardpack_core”/> <Add mover=“hardpack_boundary”/> <Add mover=“hardpack_surface”/> </PROTOCOLS>  </ROSETTASCRIPTS> </MultiplePoseMover> <MultiplePoseMover name=“MPM_min_repack” max_input_poses=“100”> <ROSETTASCRIPTS> <SCOREFXNS> <ScoreFunction name=“hard_symm_no_cst” weights=“talaris2013” symmetric=“1”/> <ScoreFunction name=“talaris_cart_sym” weights=“talaris2013_cart” symmetric=“1”/> </SCOREFXNS> <TASKOPERATIONS> <RestrictToRepacking name=“repack_only” /> </TASKOPERATIONS> <MOVERS> <SymMinMover name=“hardmin_cart” scorefxn=“talaris_cart_sym” type=“lbfgs_armijo_nonmonotone” tolerance=“0.0001” chi=“1” bb=“1” bondangle=“1” bondlength=“1” jump=“ALL” cartesian=“1”/> <SymPackRotamersMover name=“repack” scorefxn=“hard_symm_no_cst” task_operations=“repack_only” /> </MOVERS> <APPLY_TO_POSE> </APPLY_TO_POSE> <PROTOCOLS> <Add mover=“hardmin_cart” /> <Add mover=“repack” /> </PROTOCOLS>  </ROSETTASCRIPTS> </MultiplePoseMover> #minimize and repack without constrainsts on the network residues; if there is good packing around the networks, they should stay # in place in absence of the constraints. <MultiplePoseMover name=“MPM_filters” max_input_poses=“100”>  <SELECT> <AndSelector> <Filter filter=“cst_score”/> #this score represent how much the network moved during repacking without constraints <Filter filter=“uhb”/> #number of buried unsatisfied polar atoms in the entire pose <Filter filter=“holes”/> #filter out designs with large cavities </AndSelector>  </SELECT> </MultiplePoseMover> </MOVERS> <PROTOCOLS> #SETUP THE POSE #only do these first steps if starting with the python script parametric bockbones #generate the symmetric backbone <Add mover=“setup_symm”/> #transform all sidechains to Ala (need CB for minimization), then minimize with coordinate constraints on the backbone <Add mover=“transform_sc”/> #constraints on the backbone <Add mover=“add_cst”/> #minimize away bad torsions that may be present in the “ideal” generated backbone <Add mover=“hardmin_bb”/> <Add mover=“clearconstraints”/> #if using BGS, start here and comment out above: #NOW LOOK FOR NETWORKS #find h-bond networks using HBNet <Add mover_name=“hbnet_interf”/> #EVERYTHING AFTER HERE IS WITH MULTPLE_POSE_MOVER (MPM) #design the rest of the pose around the networks <Add mover_name=“MPM_design”/> #minimize and repack without the network csts turn on (this acts as a filter for networks with poor packing around them, or bad sidechains) <Add mover_name=“MPM_min_repack”/> #filters <Add mover_name=“MPM_filters”/> </PROTOCOLS> </ROSETTASCRIPTS>

Design Calculations

Parametrically generated backbones were first regularized using Cartesian space minimization in Rosetta™ to alleviate any torsional strain introduced by ideal backbone generation. For each topology, an initial search of only the inner helix was performed to identify parameter ranges that resulted in the most favorable core sidechain packing; outer helix parameters were then extensively sampled in context of these inner helix parameter ranges, generating tens of thousands of backbones. HBNet™ was used to search these backbones for hydrogen bond networks that span the intermolecular interface, have all heavy atom donors and acceptors satisfied, and contain at least three sidechains contributing hydrogen bonds. For buried interface positions, only non-charged polar amino acids were considered; for residue positions that were at least partially solvent-exposed, all polar amino acids were considered. Finer sampling was performed around backbone parameters that could accommodate both favorable hydrogen bond networks and hydrophobic packing. The helices of monomer subunits were connected into a single chain and the assembled proteins were designed using symmetric Rosetta™ sequence design calculations coupled with HBNet™ (FIG. 1F-G).

Selection Criteria and Metrics Used to Evaluate Designs

For the designs described herein, generally on the order of ˜100,000 networks were detected after Step 1, but only a handful of networks, if any, passed all of the criteria outlined in Step 2 and were carried forward. After downstream design (Step 3), packing around the networks was evaluated. Because the hydrogen bond networks are constrained during downstream design, models were minimized and sidechains repacked without the constraints to measure how well the networks remained intact in the absence of the constraints.

Lastly, models were evaluated for how closely the designed structure was recapitulated by “fold-and-dock” symmetric Rosetta™ structure predication calculations: starting from an extended chain, the energy of the assembled oligomer was optimized by Monte Carlo sampling of the internal degrees of freedom of the monomer along with the rigid body transforms relating monomer subunits in the target cyclic symmetry group. Precedence was given to designs with funnel-shaped energy landscapes, in which the ab initio predicted structures converge upon the designed structure, serving as an in silico consistency check, and checking for the possibility that the amino acid sequence can adopt alternate states. Many designs with multiple networks and high polar content at the intermolecular interfaces did not exhibit strong “funneling”, although they did exhibit large “energy gaps”, meaning that the designed structure was significantly lower in energy that any structure sampled during ab initio “fold-and-dock” calculations. Designs with large energy gaps were also considered for selection for experimental testing.

Designs selected for experimental validation were synthesized with the exact amino acid sequence resulting from the computational design method. The only exception to this was for designs lacking a Tyr or Trp residues, a Tyr was added to the surface at non-interface positions in order to monitor A₂₈₀ for purification and concentration measurements. Additionally, in a few cases, charged surface residues were modified to move the estimated isoelectric point (pI) of the protein away from buffer pH.

Loop Closure

To connect helices of the monomer into a single chain, an exhaustive database of backbone samples composed of fragments spanning two helical regions via a loop of five or less residues, as identified by DSSP, in high resolution crystallographic structures was generated. Candidate loops were identified in this database via rigid alignment of the terminal residues of the fragment and target parametrically designed backbone using an optimized superposition algorithm.

Candidates under a stringent alignment tolerance (within 0.35 Å RMSD) were then fully aligned to the target backbone via torsion-space minimization under stringent coordinate constraints to the target backbone heavy-atom coordinates and soft coordinate constraints to the aligned candidate backbone heavy-atom coordinates. Candidate loop sequences were then designed under sequence profile constraints generated via alignment of the loop backbone to the source structure database, and the lowest-scoring candidate selected as the final loop design.

Structural Analysis

Protein BLAST™ searches were performed using the National Center for Biotechnology Information (NCBI) web server, searching against all non-redundant protein sequences (‘nr’ database) using an Expect threshold (E-value cutoff) of 10.0 and the BLOSUM62 substitution matrix.

Crystal structures and design models were superimposed through structure-based alignment using all heavy atoms. From this alignment, RMSD was calculated across all alpha-carbon atoms, and also across heavy atoms of the hydrogen bond network residues.

To investigate the structural uniqueness of our designs the MICAN alignment algorithm was used to search against homo-oligomer bio-units of the same symmetry group in the Protein Data Bank (PDB).

To calculate parameters for the crystallized two-ring structures, the Coiled-coil Crick Parameterization (CCCP) web server with the “Global symmetric” optimization option as used, as structures of interest are all symmetric homooligomers. As parameters varied between the inner and outer helices of a given structure, parameters were calculated separately for inner ring and the outer ring helices, inputting .pdb files corresponding to either all helical residues of the inner ring helices, or all helical residues of the outer ring helices, for each crystal structure.

All structural images for figures were generated using PyMOL™.

Experimental Methods

Construction of Synthetic Genes

Synthetic genes were ordered from Genscript Inc. (Piscataway, N.J., USA) and delivered in either pET21-NESG or pET-28b+ E. coli expression vectors, inserted at the NdeI and XhoI sites of each vector. For the pET21-NESG constructs, synthesized DNA was cloned in frame with the C-terminal hexahistidine tag. For the pET-28b+ constructs, synthesized DNA was cloned in frame with the N-terminal hexahistidine tag and thrombin cleavage site, and a stop codon was introduced at the C-terminus. Plasmids were transformed into chemically competent E. coli BL21(DE3)Star or BL21(DE3)Star-pLysS cells (Invitrogen) for protein expression. Constructs for yeast two-hybrid assays were made by Gibson assembly; inserts were generated by PCR from pET-21 or pET-28 E. coli expression vectors as templates, or ordered as gBlocks® (IDT). All primers and gBlocks® were ordered from Integrated DNA Technologies (IDT).

Protein Expression and Purification

Starter cultures were grown at 37° C. in either Luria-Bertani (LB) medium overnight, or in Terrific Broth for 8 hours, in the presence of 50 μg/ml carbenicillin (pET21-NESG) or 30 μg/ml kanamycin (pET-28b+). Starter cultures were used to inoculate 500 mL of LB, Terrific Broth, or Terrific Broth II (MP Biomedicals) containing antibiotic. Cultures were induced with 0.2-0.5 mM IPTG at an OD600 of 0.6-0.9 and expressed overnight at 18° C. (many designs were also later expressed at 37° C. for 4 hours with no noticeable difference in yield). Cells were harvested by centrifugation for 15 minutes at 5000 rcf 4° C. and resuspended in lysis buffer (20 mM Tris, 300 mM NaCl, 20 mM Imidazole, pH 8.0 at room temperature), then lysed by sonication in presence of lysozyme, DNAse, and EDTA-free cocktail protease inhibitor (Roche) or 1 mM PMSF. Lysates were cleared by centrifugation at 4° C. 18,000 rpm for at least 30 minutes and applied to Ni-NTA (Qiagen) columns pre-equilibrated in lysis buffer. The column was washed three times with 5 column volumes (CV) of wash buffer (20 mM Tris, 300 mM NaCl, 30 mM Imidazole, pH 8.0 at room temperature), followed by 3-5 CV of high-salt wash buffer (20 mM Tris, 1 M NaCl, 30 mM Imidazole, pH 8.0 at room temperature), and then 5 CV of wash buffer. Protein was eluted with 20 mM Tris, 300 mM NaCl, 250 mM Imidazole, pH 8.0 at room temperature. Proteins were initially screened by SEC-MALS and CD with His tags intact; if possible, the tags were cleaved and samples were further purified for crystallography, SAXS, and GdmCl melts.

N-terminal hexahistidine tags of the pET-28 constructs were cleaved with restriction grade thrombin (EMD Millipore 69671-3) at room temperature for 4 hours or overnight, using a 1:5000 dilution of enzyme into sample solution; full cleavage was observed after 2 hours via SDS-PAGE analysis and no spurious cleavage was observed at time points upwards of 18 hours. Prior to addition of thrombin, buffer was exchanged into lysis buffer (20 mM Tris, 300 mM NaCl, 20 mM Imidazole). After cleavage, the sample was applied to a column of benzamidine resin (GE Healthcare/Pharmacia, Fisher #45-000-280); resin was resuspended and the sample was incubated on the column for 30-60 minutes with nutation. Flow-through was collected and additional sample was obtained by washing the benzamidine resin with 1.5 CV of lysis buffer. 1 mM PMSF was added to inhibit any remaining free thrombin. Sample was then passed over an additional Ni-NTA column and washed with 1.5 CV of lysis buffer. Proteins were further purified by FPLC size-exclusion chromatography (SEC) using a Superdex 75 10/300 column (GE Healthcare). For SAXS, gel filtration buffer was 20 mM Tris pH 8.0 at room temperature, 150 mM NaCl and 2% glycerol; for crystallography, 20 mM Tris pH 8.0, 100 mM NaCl was used. No reducing agents were added, as none of the designed proteins contained cysteines.

Size-Exclusion Chromatography, Multi-Angle Light Scattering (SEC-MALS)

SEC-MALS experiments used a Superdex 75 10/300 column connected to a miniDAWN TREOS multi-angle static light scattering and an Optilab T-rEX (refractometer with Extended range) detector (Wyatt Technology Corporation, Santa Barbara Calif., USA). Protein samples were injected at concentrations of 3-5 mg/mL in TBS (pH 8.0) or PBS (pH 7.4). Data was analyzed using ASTRA™ (Wyatt Technologies) software to estimate the weigh average molar mass (M_(w)) of eluted species, as well as the number average molar mass (M_(n)) to assess monodispersity by polydispersity index (PDI)=M_(w)/M_(n).

Circular Dichroism (CD) Measurements

CD wavelength scans (260 to 195 nm) and temperature melts (25 to 95° C.) were measured using a JASCO J-1500 or an AVIV model 420 CD spectrometer. Temperature melts monitored absorption signal at 222 nm and were carried out at a heating rate of 4° C./min; protein samples were at 0.2-0.5 mg/mL in phosphate buffered saline (PBS) pH 7.4 in a 0.1 cm cuvette.

Guanidinium chloride (GdmCl) titrations were performed on the same spectrometers with automated titration apparatus in PBS pH 7.4 at 25° C., monitored at 222 nm, using a protein concentration of 0.025-0.06 mg/mL in a 1 cm cuvette with stir bar; each titration consisted of at least 40 evenly distributed concentration points with one minute mixing time for each step. Titrant solution consisted of the same concentration of protein in PBS+GdmCl; GdmCl concentration was determined by refractive index.

Inner Helix Peptides

Peptides 2L4HC2_9_inner and 2L6HC3_13_inner were ordered from Genscript Inc. (Piscataway, N.J., USA) with N-terminal acetylation and C-terminal amidation. 2L4HC2_9_inner=SSDYLRETIEELRERIRELEREIRRSNEEIERLREEKS (SEQ ID NO: 93) and 2L6HC3_13_inner=TERENNYRNEENNRKIEEEIREJKKEIKKNKERD (SEQ ID NO: 94). Peptides were dissolved in PBS pH 7.4 and further dialyzed into PBS pH 7.4 for CD experiments.

Crystallization of Protein Samples

Purified protein samples were concentrated to approximately 12 mg/ml in 20 mM Tris pH 8.0 and 100 mM NaCl. Samples were screened using the sparse matrix method (Jancarik and Kim, 1991) with a Phoenix Robot (Art Robbins Instruments, Sunnyvale, Calif.) utilizing the following crystallization screens: Berkeley Screen (Lawrence Berkeley National Laboratory), Crystal Screen, PEG/Ion, Index and PEGRx (Hampton Research, Aliso Viejo, Calif.). The optimum conditions for crystallization of the different designs were found as follows: 2L6HC3_6, 0.2 M Sodium Fluoride, 0.1 M MES pH 5.5 and 20% PEG 400; 2L6HC3_12, 2.2 M Sodium Malonate pH 5.0; 2L6HC3_3, 0.06 M Citric acid, 0.04 M BIS-TRIS propane pH 4.1 and 16% PEG 3,350; 2L8HC4_0.12, 0.2 M Sodium Acetate trihydrate, 0.1 M Tris hydrochloride pH 8.5 and 30% PEG 4,000; 3L6HC2_2, 0.1 M Sodium Acetate trihydrate pH 4.5 and 3.0 M Sodium chloride; 2L4HC2_23, 0.2 M Lithium chloride and 20% PEG 3,350; 2L4HC2_9, 0.1 M Sodium citrate tribasic dehydrate pH 5.0, 30% PEG MME 550; 2L4HC2_11, 0.1 M Tris pH 8.5 and 2.0 M Ammonium sulfate; 5L6HC3_1, 0.1 M Citric acid pH 3.5 and 3.0 M Sodium chloride; and 2L4HC2_24 was concentrated to 20 mg/ml and crystallized in 0.1 M Citric acid pH 3.5, 2.0 M Ammonium sulfate. Crystals were obtained after 1 to 14 days by the sitting-drop vapor-diffusion method with the drops consisting of a 1:1 mixture of 0.2 μL protein solution and 0.2 μL reservoir solution.

X-Ray Data Collection and Structure Determination

The crystals of the designed proteins were placed in a reservoir solution containing 15 to 20% (v/v) glycerol, and then flash-cooled in liquid nitrogen. The X-ray data sets were collected at the Berkeley Center for Structural Biology beamlines 5.0.1, 8.2.1 and 8.2.2 of the Advanced Light Source at Lawrence Berkeley National Laboratory (LBNL). Data sets were indexed and scaled using HKL2000. All the design structures were determined by the molecular-replacement method with the program PHASER within the Phenix suite using the design models as the initial search model. The atomic positions obtained from molecular replacement and the resulting electron density maps were used to build the design structures and initiate crystallographic refinement and model rebuilding. Structure refinement was performed using the phenix.refine program. Manual rebuilding using COOT and the addition of water molecules allowed construction of the final models. Root-mean-square deviation differences from ideal geometries for bond lengths, angles and dihedrals were calculated with Phenix. The overall stereochemical quality of all final models was assessed using the program MOLPROBIY.

Small Angle X-Ray Scattering (SAXS)

Samples were purified by gel filtration in 20 mM Tris pH 8.0 at room temperature, 150 mM NaCl and 2% glycerol; fractions preceding the void volume of the column were used as blanks for buffer subtraction. Scattering measurements were performed at the SIBYLS 12.3.1 beamline at the Advanced Light Source. The X-ray wavelength (λ) was 1 Å, and the sample-to-detector distance of the Mar16S detector was 1.5 m, corresponding to a scattering vector q (q=4π sin θ/1, where 2θ is the scattering angle) range of 0.01 to 0.3 Å-1. Data sets were collected using exposures of 0.5, 1, and 6 seconds at 12 keV. For longer exposures that resulted in saturation of low q signal or radiation damage, datasets were merged with lower exposures from the same sample. For each sample, data was collected for at least two different concentrations to test for concentration-dependent effects; “high” concentration samples ranged from 3-7 mg/ml and “low” concentration samples ranged from 1-2 mg/ml. Data was analyzed using the ScÅtter software package as previously described; for samples that did not exhibit concentration-dependence, the best data set based on signal-to-noise and Guinier fitting was used for analysis. FoXS was used to compare design models to experimental scattering profiles and calculate quality of fit (X) values. For the design models, extra residues introduced by the expression vector were added to the computational models using Rosetta™ Remodel so that the design sequence matched that of the experimental sample. To capture the conformational flexibility of these extra tag residues in solution, 100 independent models were generated per design. These 100 models were then clustered by Rosetta™, and to avoid bias, the cluster center of the largest cluster was selected as the single representative model used for fitting to experimental data.

Yeast Two-Hybrid

Protein binders were cloned into plasmids bearing the GAL4 DNA-binding domain (pOBD2) and or the GAL4 transcription activation domain (poAD) using Gibson assembly and sequence verified. For each pair of binders tested, the yeast strain PJ69-4a was transformed with the appropriate pair of plasmids using a modified LiOAc transformation protocol where rescue and selection of the transformed yeast was performed in minimal liquid media lacking tryptophan and leucine. Before the assay, transformed cells were diluted 1:10 and grown for 16 hours in fresh minimal media lacking tryptophan and leucine. After this initial incubation, cells were diluted again 1:10 and grown—while shaking—in a 96 well plate, this time in 200 μl of minimal media lacking tryptophan, leucine and histidine. Since a protein interaction between the DNA-binding domain and the transcription activation domain is necessary for the cells to grow in the absence of histidine, successful interactions can be approximated by growth rate. The optical density (OD) of cells was measured every 10 minutes over the span of 48 hours, and the growth rate was calculated for every 60-minute span. The maximum growth rate per hour (maxV) was used as a proxy for interactions between binder pairs.

Mass Spectrometry

Gel bands were isolated, washed with ammonium bicarbonate, and reduced with DTT at 60° C. for 15 minutes. After cooling, gel pieces were treated with iodoacetamide for 15 minutes, in the dark at room temperature, to alkylate reduced thiol groups. Protease digestion was accomplished with sequencing grade trypsin at 10:1, substrate to enzyme, concentration for 4 hours at 37° C. Peptide samples were dried under vacuum and resuspended in 0.1% formic acid prior to LCMS/MS analysis. Liquid chromatography consisted of a 60-minute gradient across a 15 cm column packed with C18 resin downstream of a 3 cm kasil frit trap packed with C12 resin. Spectra were collected using data-dependent acquisition on a Thermo Velos Pro mass spectrometer. Each sample was injected with three technical replicates and peptides were identified using SEQUEST and Percolator followed by IDPicker for protein inference.

In a further aspect, a method is provided. A computing device determines a search space for hydrogen bond networks related to one or more molecules. The search space includes a plurality of energy terms related to a plurality of residues related to the hydrogen bond networks. The computing device searches the search space to identify one or more hydrogen bond networks based on the plurality of energy terms. The computing device screens the identified one or more hydrogen bond networks to identify one or more screened hydrogen bond networks based on scores for the one or more identified hydrogen bond networks. The computing device generates an output related to the one or more screened hydrogen bond networks.

In another aspect, a computing device is provided. The computing device includes one or more data processors and a computer-readable medium. The computer-readable medium is configured to store at least computer-readable instructions that, when executed, cause the computing device to perform functions. The functions include: determining a search space for hydrogen bond networks related to one or more molecules, where the search space includes a plurality of energy terms related to a plurality of residues related to the hydrogen bond networks; searching the search space to identify one or more hydrogen bond networks based on the plurality of energy terms; screening the identified one or more hydrogen bond networks to identify one or more screened hydrogen bond networks based on scores for the one or more identified hydrogen bond networks; and generating an output related to the one or more screened hydrogen bond networks.

In another aspect, a computer-readable medium is provided. The computer-readable medium is configured to store at least computer-readable instructions that, when executed by one or more processors of a computing device, cause the computing device to perform functions. The functions include: determining a search space for hydrogen bond networks related to one or more molecules, where the search space includes a plurality of energy terms related to a plurality of residues related to the hydrogen bond networks; searching the search space to identify one or more hydrogen bond networks based on the plurality of energy terms; screening the identified one or more hydrogen bond networks to identify one or more screened hydrogen bond networks based on scores for the one or more identified hydrogen bond networks; and generating an output related to the one or more screened hydrogen bond networks.

In another aspect, an apparatus is provided. The apparatus includes: means for determining a search space for hydrogen bond networks related to one or more molecules, where the search space includes a plurality of energy terms related to a plurality of residues related to the hydrogen bond networks; means for searching the search space to identify one or more hydrogen bond networks based on the plurality of energy terms; means for screening the identified one or more hydrogen bond networks to identify one or more screened hydrogen bond networks based on scores for the one or more identified hydrogen bond networks; and means for generating an output related to the one or more screened hydrogen bond networks.

Example Computing Environment

FIG. 6 is a block diagram of an example computing network. Some or all of the above-mentioned techniques disclosed herein, such as but not limited to techniques disclosed as part of and/or being performed by software, the Rosetta™ software suite, RosettaDesign™, Rosetta™ applications, and/or other herein-described computer software and computer hardware, can be part of and/or performed by a computing device. For example, FIG. 6 shows protein design system 602 configured to communicate, via network 606, with client devices 604 a, 604 b, and 604 c and protein database 608. In some embodiments, protein design system 602 and/or protein database 608 can be a computing device configured to perform some or all of the herein described methods and techniques, such as but not limited to, method 800 and functionality described as being part of or related to Rosetta™. Protein database 608 can, in some embodiments, store information related to and/or used by Rosetta™.

Network 606 may correspond to a LAN, a wide area network (WAN), a corporate intranet, the public Internet, or any other type of network configured to provide a communications path between networked computing devices. Network 606 may also correspond to a combination of one or more LANs, WANs, corporate intranets, and/or the public Internet.

Although FIG. 6 only shows three client devices 604 a, 604 b, 604 c, distributed application architectures may serve tens, hundreds, or thousands of client devices. Moreover, client devices 604 a, 604 b, 604 c (or any additional client devices) may be any sort of computing device, such as an ordinary laptop computer, desktop computer, network terminal, wireless communication device (e.g., a cell phone or smart phone), and so on. In some embodiments, client devices 604 a, 604 b, 604 c can be dedicated to problem solving/using the Rosetta™ software suite. In other embodiments, client devices 604 a, 604 b, 604 c can be used as general purpose computers that are configured to perform a number of tasks and need not be dedicated to problem solving/using Rosetta™. In still other embodiments, part or all of the functionality of protein design system 602 and/or protein database 608 can be incorporated in a client device, such as client device 604 a, 604 b, and/or 604 c.

Computing Environment Architecture

FIG. 7A is a block diagram of an example computing device (e.g., system). In particular, computing device 700 shown in FIG. 7A can be configured to: include components of and/or perform one or more functions of protein design system 602, client device 604 a, 604 b, 604 c, network 606, and/or protein database 608 and/or carry out part or all of any herein-described methods and techniques, such as but not limited to method 800. Computing device 700 may include a user interface module 701, a network-communication interface module 702, one or more processors 703, and data storage 704, all of which may be linked together via a system bus, network, or other connection mechanism 705.

User interface module 701 can be operable to send data to and/or receive data from external user input/output devices. For example, user interface module 701 can be configured to send and/or receive data to and/or from user input devices such as a keyboard, a keypad, a touch screen, a computer mouse, a track ball, a joystick, a camera, a voice recognition module, and/or other similar devices. User interface module 701 can also be configured to provide output to user display devices, such as one or more cathode ray tubes (CRT), liquid crystal displays (LCD), light emitting diodes (LEDs), displays using digital light processing (DLP) technology, printers, light bulbs, and/or other similar devices, either now known or later developed. User interface module 701 can also be configured to generate audible output(s), such as a speaker, speaker jack, audio output port, audio output device, earphones, and/or other similar devices.

Network-communications interface module 702 can include one or more wireless interfaces 707 and/or one or more wireline interfaces 708 that are configurable to communicate via a network, such as network 606 shown in FIG. 6. Wireless interfaces 707 can include one or more wireless transmitters, receivers, and/or transceivers, such as a Bluetooth transceiver, a Zigbee transceiver, a Wi-Fi transceiver, a WiMAX transceiver, and/or other similar type of wireless transceiver configurable to communicate via a wireless network. Wireline interfaces 708 can include one or more wireline transmitters, receivers, and/or transceivers, such as an Ethernet transceiver, a Universal Serial Bus (USB) transceiver, or similar transceiver configurable to communicate via a twisted pair, one or to more wires, a coaxial cable, a fiber-optic link, or a similar physical connection to a wireline network.

In some embodiments, network communications interface module 702 can be configured to provide reliable, secured, and/or authenticated communications. For each communication described herein, information for ensuring reliable communications (i.e., guaranteed message delivery) can be provided, perhaps as part of a message header and/or footer (e.g., packet/message sequencing information, encapsulation header(s) and/or footer(s), size/time information, and transmission verification information such as CRC and/or parity check values). Communications can be made secure (e.g., be encoded or encrypted) and/or decrypted/decoded using one or more cryptographic protocols and/or algorithms, such as, but not limited to, DES, AES, RSA, Diffie-Hellman, and/or DSA. Other cryptographic protocols and/or algorithms can be used as well or in addition to those listed herein to secure (and then decrypt/decode) communications.

Processors 703 can include one or more general purpose processors and/or one or more special purpose processors (e.g., digital signal processors, application specific integrated circuits, etc.). Processors 703 can be configured to execute computer-readable program instructions 706 contained in data storage 704 and/or other instructions as described herein. Data storage 704 can include one or more computer-readable storage media that can be read and/or accessed by at least one of processors 703. The one or more computer-readable storage media can include volatile and/or non-volatile storage components, such as optical, magnetic, organic or other memory or disc storage, which can be integrated in whole or in part with at least one of processors 703. In some embodiments, data storage 704 can be implemented using a single physical device (e.g., one optical, magnetic, organic or other memory or disc storage unit), while in other embodiments, data storage 704 can be implemented using two or more physical devices.

Data storage 704 can include computer-readable program instructions 706 and perhaps additional data. For example, in some embodiments, data storage 704 can store part or all of data utilized by a protein design system and/or a protein database; e.g., protein designs system 602, protein database 608. In some embodiments, data storage 704 can additionally include storage required to perform at least part of the herein-described methods and techniques and/or at least part of the functionality of the herein-described devices and networks.

FIG. 7B depicts a network 606 of computing clusters 709 a, 709 b, 709 c arranged as a cloud-based server system in accordance with an example embodiment. Data and/or software for protein design system 602 can be stored on one or more cloud-based devices that store program logic and/or data of cloud-based applications and/or services. In some embodiments, protein design system 602 can be a single computing device residing in a single computing center. In other embodiments, protein design system 602 can include multiple computing devices in a single computing center, or even multiple computing devices located in multiple computing centers located in diverse geographic locations.

In some embodiments, data and/or software for protein design system 602 can be encoded as computer readable information stored in tangible computer readable media (or computer readable storage media) and accessible by client devices 604 a, 604 b, and 604 c, and/or other computing devices. In some embodiments, data and/or software for protein design system 602 can be stored on a single disk drive or other tangible storage media, or can be implemented on multiple disk drives or other tangible storage media located at one or more diverse geographic locations.

FIG. 7B depicts a cloud-based server system in accordance with an example embodiment. In FIG. 7B, the functions of protein design system 602 can be distributed among three computing clusters 709 a, 709 b, and 709 c. Computing cluster 709 a can include one or more computing devices 700 a, cluster storage arrays 710 a, and cluster routers 711 a connected by a local cluster network 712 a. Similarly, computing cluster 709 b can include one or more computing devices 700 b, cluster storage arrays 710 b, and cluster routers 711 b connected by a local cluster network 712 b. Likewise, computing cluster 709 c can include one or more computing devices 700 c, cluster storage arrays 710 c, and cluster routers 711 c connected by a local cluster network 712 c.

In some embodiments, each of the computing clusters 709 a, 709 b, and 709 c can have an equal number of computing devices, an equal number of cluster storage arrays, and an equal number of cluster routers. In other embodiments, however, each computing cluster can have different numbers of computing devices, different numbers of cluster storage arrays, and different numbers of cluster routers. The number of computing devices, cluster storage arrays, and cluster routers in each computing cluster can depend on the computing task or tasks assigned to each computing cluster.

In computing cluster 709 a, for example, computing devices 700 a can be configured to perform various computing tasks of protein design system 602. In one embodiment, the various functionalities of protein design system 602 can be distributed among one or more of computing devices 700 a, 700 b, and 700 c. Computing devices 700 b and 700 c in computing clusters 709 b and 709 c can be configured similarly to computing devices 700 a in computing cluster 709 a. On the other hand, in some embodiments, computing devices 700 a, 700 b, and 700 c can be configured to perform different functions.

In some embodiments, computing tasks and stored data associated with protein design system 602 can be distributed across computing devices 700 a, 700 b, and 700 c based at least in part on the processing requirements of protein design system 602, the processing capabilities of computing devices 700 a, 700 b, and 700 c, the latency of the network links between the computing devices in each computing cluster and between the computing clusters themselves, and/or other factors that can contribute to the cost, speed, fault-tolerance, resiliency, efficiency, and/or other design goals of the overall system architecture.

The cluster storage arrays 710 a, 710 b, and 710 c of the computing clusters 709 a, 709 b, and 709 c can be data storage arrays that include disk array controllers configured to manage read and write access to groups of hard disk drives. The disk array controllers, alone or in conjunction with their respective computing devices, can also be configured to manage backup or redundant copies of the data stored in the cluster storage arrays to protect against disk drive or other cluster storage array failures and/or network failures that prevent one or more computing devices from accessing one or more cluster storage arrays.

Similar to the manner in which the functions of protein design system 602 can be distributed across computing devices 700 a, 700 b, and 700 c of computing clusters 709 a, 709 b, and 709 c, various active portions and/or backup portions of these components can be distributed across cluster storage arrays 710 a, 710 b, and 710 c. For example, some cluster storage arrays can be configured to store one portion of the data and/or software of protein design system 602, while other cluster storage arrays can store a separate portion of the data and/or software of protein design system 602. Additionally, some cluster storage arrays can be configured to store backup versions of data stored in other cluster storage arrays.

The cluster routers 711 a, 711 b, and 711 c in computing clusters 709 a, 709 b, and 709 c can include networking equipment configured to provide internal and external communications for the computing clusters. For example, the cluster routers 711 a in computing cluster 709 a can include one or more internet switching and routing devices configured to provide (i) local area network communications between the computing devices 700 a and the cluster storage arrays 701 a via the local cluster network 712 a, and (ii) wide area network communications between the computing cluster 709 a and the computing clusters 709 b and 709 c via the wide area network connection 713 a to network 606. Cluster routers 711 b and 711 c can include network equipment similar to the cluster routers 711 a, and cluster routers 711 b and 711 c can perform similar networking functions for computing clusters 709 b and 709 b that cluster routers 711 a perform for computing cluster 709 a.

In some embodiments, the configuration of the cluster routers 711 a, 711 b, and 711 c can be based at least in part on the data communication requirements of the computing devices and cluster storage arrays, the data communications capabilities of the network equipment in the cluster routers 711 a, 711 b, and 711 c, the latency and throughput of local networks 712 a, 712 b, 712 c, the latency, throughput, and cost of wide area network links 713 a, 713 b, and 713 c, and/or other factors that can contribute to the cost, speed, fault-tolerance, resiliency, efficiency and/or other design goals of the moderation system architecture.

Example Methods of Operation

FIG. 8 is a flow chart of an example method 800. Method 800 can be carried out by a computing device, such as computing device 700 described in the context of at least FIG. 7A Method 800 can begin at block 810, where the computing device can determine a search space for hydrogen bond networks related to one or more molecules, where the search space includes a plurality of energy terms related to a plurality of residues related to the hydrogen bond networks, such as discussed above at least in the “Computational Techniques” section.

In some embodiments, the search space can be configured as a graph having a plurality of nodes connected by one or more edges, where a node of the plurality of nodes is based on a particular residue of the plurality of residues, the particular residue having a residue position, and where an edge of the one or more edges connects a first node and a second node of the plurality of nodes based on a possible interaction between the first and second nodes, such as discussed above at least in the “Computational Techniques” section. In particular of these embodiments, the first node can relate to a first residue of the plurality of residues, where the second node relates to a second residue of the plurality of residues, and where the possible interaction between first and second nodes relate to a possible interaction between a rotamer of the first residue and/or a rotamer of the second residue, such as discussed above at least in the “Computational Techniques” section. In more particular of these embodiments, the possible interaction between the possible interaction between first and second nodes can relate to an interaction energy between the first residue and the second residue, such as discussed above at least in the “Computational Techniques” section. In even more particular of these embodiments, determining the search space can include: determining whether the interaction energy between the first residue and the second residue is less than a threshold interaction energy; and after determining that the interaction energy between the first residue and the second residue is less than the threshold interaction energy, adding a hydrogen bond network including the first node, the second node, and at least one edge between the first and second nodes to the search space, such as discussed above at least in the “Computational Techniques” section. In further more particular of these embodiments, at least one edge between the first and second nodes can include information about the interaction energy between the first residue and the second residue, such as discussed above at least in the “Computational Techniques” section. In even further particular of these embodiments, the information about the interaction energy between the first residue and the second residue can include a plurality of interaction energy values, where each interaction energy value in the plurality of interaction energy values is associated with a particular rotamer of the first residue and a particular rotamer of the second residue, such as discussed above at least in the “Computational Techniques” section.

In other embodiments, determining the search space can include: determining at least a first residue position and a second residue position at an intermolecular interface between a first molecule and a second molecule, the first residue position associated with a first residue of the first molecule and the second residue position associated with a second residue of the second molecule; and determining the search space based on the at least the first residue position and the second residue position, such as discussed above at least in the “Computational Techniques” section. In some of these embodiments, at least one of the first molecule and the second molecule can include a polypeptide chain, such as discussed above at least in the “Computational Techniques” section.

At block 820, the computing device can search the search space to identify one or more hydrogen bond networks based on the plurality of energy terms, such as discussed above at least in the “Computational Techniques” section. In some embodiments, searching the search space includes searching all of the search space, such as discussed above at least in the “Computational Techniques” section. In particular of these embodiments, searching all of the search space using the depth-first search. In other particular of these embodiments, searching all of the search space includes searching all of the search space using a breadth-first search, such as discussed above at least in the “Computational Techniques” section.

In other embodiments, searching the search space can include: performing a first search of the search space to identify one or more initial hydrogen bond networks; and identifying the one or more identified hydrogen bond networks by at least merging a first hydrogen bond network and a second hydrogen bond network of the one or more initial hydrogen bond networks, such as discussed above at least in the “Computational Techniques” section. In particular of these embodiments, merging the first hydrogen bond network and the second hydrogen bond network can include: determining whether the first hydrogen bond network and the second hydrogen bond network share an identical rotamer; and after determining that the first hydrogen bond network and the second hydrogen bond network share an identical rotamer, merging the first hydrogen bond network and the second hydrogen bond network, such as discussed above at least in the “Computational Techniques” section.

At block 830, the computing device can screening the identified one or more hydrogen bond networks to identify one or more screened hydrogen bond networks based on scores for the one or more identified hydrogen bond networks, such as discussed above at least in the “Computational Techniques” section. In some embodiments, a particular score for a particular identified hydrogen bond network of the one or more identified hydrogen bond networks can be based on a number of polar atoms that participate in the particular hydrogen bond network, such as discussed above at least in the “Computational Techniques” section. In other embodiments, a particular score for a particular identified hydrogen bond network of the one or more identified hydrogen bond networks can be based on a background reference structure, such as discussed above at least in the “Computational Techniques” section. In particular of these embodiments, the particular score for the particular identified hydrogen bond network can be based on a score related to one or more sidechain-backbone hydrogen bonds, where the one or more sidechain-backbone hydrogen bonds can be related to the background reference structure, such as discussed above at least in the “Computational Techniques” section. In still other embodiments, a particular score for a particular identified hydrogen bond network of the one or more identified hydrogen bond networks can be based on an energy function, such as discussed above at least in the “Computational Techniques” section.

At block 840, an output related to the one or more screened hydrogen bond networks can be generated. In some embodiments, generating the output related to the one or more screened hydrogen bond networks can include designing one or more molecules based on the screened hydrogen bond networks, such as discussed above at least in the “Computational Techniques” section. In particular of these embodiments, designing the one or more molecules based on the screened hydrogen bond networks includes allowing one or more relatively-small movements of one or more rotamers in a screened hydrogen bond network, such as discussed above at least in the “Computational Techniques” section.

In other embodiments, generating the output related to the one or more screened to hydrogen bond networks can include generating a plurality of outputs related to the one or more screened hydrogen bond networks, such as discussed above at least in the “Computational Techniques” section. In still other embodiments, generating the output related to the one or more screened hydrogen bond networks can include: generating a synthetic gene that is based on the one or more screened hydrogen bond networks; expressing a particular protein in vivo using the synthetic gene; and purifying the particular protein. In particular of these embodiments, expressing the particular protein sequence in vivo using the synthetic gene includes expressing the particular protein sequence in one or more Escherichia coli that include the synthetic gene, such as discussed above in at least in the “Experimental Methods” section.

The particulars shown herein are by way of example and for purposes of illustrative discussion of the preferred embodiments of the present invention only and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects of various embodiments of the invention. In this regard, no attempt is made to show structural details of the invention in more detail than is necessary for the fundamental understanding of the invention, the description taken with the drawings and/or examples making apparent to those skilled in the art how the several forms of the invention may be embodied in practice.

The above definitions and explanations are meant and intended to be controlling in any future construction unless clearly and unambiguously modified in the following examples or when application of the meaning renders any construction meaningless or essentially meaningless. In cases where the construction of the term would render it meaningless or essentially meaningless, the definition should be taken from Webster's Dictionary, 3^(rd) Edition or a dictionary known to those of skill in the art, such as the Oxford Dictionary of Biochemistry and Molecular Biology (Ed. Anthony Smith, Oxford University Press, Oxford, 2004).

As used herein and unless otherwise indicated, the terms “a” and “an” are taken to mean “one”, “at least one” or “one or more”. Unless otherwise required by context, singular terms used herein shall include pluralities and plural terms shall include the singular.

Unless the context clearly requires otherwise, throughout the description and the claims, the words ‘comprise’, ‘comprising’, and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to”. Words using the singular or plural number also include the plural or singular number, respectively. Additionally, the words “herein,” “above” and “below” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application.

The above description provides specific details for a thorough understanding of, and enabling description for, embodiments of the disclosure. However, one skilled in the art will understand that the disclosure may be practiced without these details. In other instances, well-known structures and functions have not been shown or described in detail to avoid unnecessarily obscuring the description of the embodiments of the disclosure. The description of embodiments of the disclosure is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. While specific embodiments of, and examples for, the disclosure are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize.

All of the references cited herein are incorporated by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions and concepts of the above references and application to provide yet further embodiments of the disclosure. These and other changes can be made to the disclosure in light of the detailed description.

Specific elements of any of the foregoing embodiments can be combined or substituted for elements in other embodiments. Furthermore, while advantages associated with certain embodiments of the disclosure have been described in the context of these embodiments, other embodiments may also exhibit such advantages, and not all embodiments need necessarily exhibit such advantages to fall within the scope of the disclosure.

The above detailed description describes various features and functions of the disclosed systems, devices, and methods with reference to the accompanying figures. In the figures, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, figures, and claims are not meant to be limiting. Other embodiments can be utilized, and other changes can be made, without departing from the spirit or scope of the subject matter presented herein. It will be readily understood that the aspects of the present disclosure, as generally described herein, and illustrated in the figures, can be arranged, substituted, combined, separated, and designed in a wide variety of different configurations, all of which are explicitly contemplated herein.

With respect to any or all of the ladder diagrams, scenarios, and flow charts in the figures and as discussed herein, each block and/or communication may represent a processing of information and/or a transmission of information in accordance with example embodiments. Alternative embodiments are included within the scope of these example embodiments. In these alternative embodiments, for example, functions described as blocks, transmissions, communications, requests, responses, and/or messages may be executed out of order from that shown or discussed, including substantially concurrent or in reverse order, depending on the functionality involved. Further, more or fewer blocks and/or functions may be used with any of the ladder diagrams, scenarios, and flow charts discussed herein, and these ladder diagrams, scenarios, and flow charts may be combined with one another, in part or in whole.

A block that represents a processing of information may correspond to circuitry that can be configured to perform the specific logical functions of a herein-described method or technique. Alternatively or additionally, a block that represents a processing of information may correspond to a module, a segment, or a portion of program code (including related data). The program code may include one or more instructions executable by a processor for implementing specific logical functions or actions in the method or technique. The program code and/or related data may be stored on any type of computer readable medium such as a storage device including a disk or hard drive or other storage medium.

The computer readable medium may also include non-transitory computer readable media such as computer-readable media that stores data for short periods of time like register memory, processor cache, and random access memory (RAM). The computer readable media may also include non-transitory computer readable media that stores program code and/or data for longer periods of time, such as secondary or persistent long term storage, like read only memory (ROM), optical or magnetic disks, compact-disc read only memory (CD-ROM), for example. The computer readable media may also be any other volatile or non-volatile storage systems. A computer readable medium may be considered a computer readable storage medium, for example, or a tangible storage device. Moreover, a block that represents one or more information transmissions may correspond to information transmissions between software and/or hardware modules in the same physical device. However, other information transmissions may be between software modules and/or hardware modules in different physical devices.

Numerous modifications and variations of the present disclosure are possible in light of the above teachings.

The particulars shown herein are by way of example and for purposes of illustrative discussion of the preferred embodiments of the present invention only and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects of various embodiments of the invention. In this regard, no attempt is made to show structural details of the invention in more detail than is necessary for the fundamental understanding of the invention, the description taken with the drawings and/or examples making apparent to those skilled in the art how the several forms of the invention may be embodied in practice. 

We claim:
 1. A polypeptide comprising the amino acid sequence of Formula I: Z1-Z2-Z3-Z4-Z5, wherein: Z1 is a helix initiating sequence comprising the amino acid sequence of Formula 2: J1-J2-J3, wherein J1 is selected from the group consisting of S, T, N, and D; J2 is selected from the group consisting of P, E, R, K, L, A; and J3 is selected from the group consisting of E, D, R, K, L, V, A, S, T, Y, or is absent; Z3 is a helix connecting sequence having the amino acid sequence of Formula 3: (SEQ ID NO: 1) [RKED]-L-[NQEDRKST]-[NQEDRKST]-[NQEDRKST]-G- [STNQED]-[STNQED]-[STND]-E-[EDRK]-V-[RKED];

Z5 is a helix terminating sequence comprising the amino acid sequence of Formula 4: xx-xx-[RKEDSTNQYA];

Z2 is selected from the group consisting of general formulae BX₁BX₂, X₁BBX₂, X₁BX₂B, X₁X₂BB, BX₁X₂B, and BBX₁X₂, wherein: B is xx-S-L-xx-xx-Q-xx; X₁ and X₂ independently have the amino acid sequence of Formula 5: O₁O₂O₃O₄O₅O₆O₇ wherein: O₁, O₄, O₅, and O₇ are xx; O₂ and O₃ are independently selected from the group consisting of I, L, and A; and O₆ is L; and Z4 is selected from the group consisting of general formulae B₂X₃B₂X₄, X₃B₂B₂X₄, X₃B₂X₄B₂, X₃X₄B₂B₂, B₂X₃X₄B₂, and B₂B₂X₃X₄, wherein B₂ is xx-L-A-xx-xx-Q-xx; and X₃ and X₄ independently have the amino acid sequence of Formula 6: O₁₀O₁₁O₁₂O₁₃O₁₄O₁₅O₁₆ wherein O₁₀, O₁₃, O₁₄, and O₁₆ are xx; O₁₁ is L; and O₁₂ and O₁₅ are independently selected from e group consisting of I, L, V, and A; wherein xx is any amino acid; and wherein: (i) when Z2 is BX₁BX₂ then Z4 is X₃B₂X₄B₂; (ii) when Z2 is X₁BBX₂ then Z4 is X₃B₂B₂X₄; (iii) when Z2 is X₁BX₂B then Z4 is BX₃B₂X₄; (iv) when Z2 is X₁X₂BB then Z4 is B₂B₂X₃X₄; (v) when Z2 is BX₁X₂B then Z4 is B₂X₃X₄B₂; (vi) when Z2 is BBX₁X₂ then Z4 is X₃X₄B₂B₂; and (vii) “and” is not used interchangeably with “or”.
 2. The polypeptide of claim 1, wherein J3 is present.
 3. The polypeptide of claim 1, wherein Z1 is TRT.
 4. The polypeptide of claim 1, wherein Z3 is RLQREGSSDEDVR (SEQ ID NO: 81).
 5. The polypeptide of claim 1, wherein Z5 is RQD.
 6. The polypeptide of claim 1, wherein B is RSLREQE (SEQ ID NO: 82).
 7. The polypeptide of claim 1, wherein O₁, O₄, O₅, and O₇ are independently selected from the group consisting of E, R, and K; wherein “and” is not used interchangeably with “or”.
 8. The polypeptide of claim 1, wherein X₁ and X₂ are independently selected from the group consisting of EIIRELE (SEQ ID NO: 83), ELLRELE (SEQ ID NO: 84), and ELAKRLK (SEQ ID NO: 85); wherein “and” is not used interchangeably with “or”.
 9. The polypeptide of claim 1, wherein B₂ is KLAREQK (SEQ ID NO: 86).
 10. The polypeptide of claim 1, wherein O₁₂ and O₁₅ are independently selected from the group consisting of I, L, and V; wherein “and” is not used interchangeably with “or”.
 11. The polypeptide of claim 1, wherein X₃ and X₄ are independently selected from the group consisting of [YE]-LVEELK (SEQ ID NO: 87), [YE]-LLREIK (SEQ ID NO: 88), [YE]-LVEEIE (SEQ ID NO: 89), ELVEELK (SEQ ID NO: 90), ELLREIK (SEQ ID NO: 91), and ELVEEIE (SEQ ID NO: 92); wherein “and” is not used interchangeably with “or”.
 12. The polypeptide of claim 1, wherein Z2 is selected from the group consisting of general formulae BX₁BX₂, X₁BBX₂, X₁BX₂B, and X₁X₂BB; and Z4 is selected from the group consisting of general formulae B₂X₃B₂X₄, X₃B₂B₂X₄, X₃B₂X₄B₂, and X₃X₄B₂B₂; wherein “and” is not used interchangeably with “or”.
 13. The polypeptide of claim 1, comprising a polypeptide that is at least 75% identical over its full length to the amino acid sequence selected from the group consisting of SEQ ID NOS:2-5.
 14. The polypeptide of claim 1, linked to a cargo.
 15. The polypeptide of claim 1, comprising a homo-oligomer of the polypeptide.
 16. A polypeptide that is at least 75% identical over its full length to the amino acid sequence selected from the group consisting of SEQ ID NOS:2-79.
 17. The polypeptide of claim 16, which is at least 90% identical over its full length to the amino acid sequence selected from the group consisting of SEQ ID NOS:2-79.
 18. The polypeptide of claim 16, which is at least 95% identical over its full length to the amino acid sequence selected from the group consisting of SEQ H) NOS:2-79.
 19. The polypeptide of claim 16, which is at least 100% identical over its full length to the amino acid sequence selected from the group consisting of SEQ ID NOS:2-79.
 20. A polypeptide that is at least 75% identical over its full length to the amino add sequence of SEQ ID NO:
 24. 21. The polypeptide of claim 20, wherein the polypeptide comprises the amino acid sequence of SEQ ID NO:24. 